[main] Source code updates from dotnet/dotnet

[dotnet-maestro]

Note

This is a codeflow update. It may contain both source code changes from
the VMR
as well as dependency updates. Learn more here.

This pull request brings the following source code changes

From https://github.com/dotnet/dotnet

• Subscription: 94ba9a9b-a084-4c1e-bf44-d0c711c17773
• Build: 20260326.6 (307929)
• Date Produced: March 26, 2026 4:26:20 PM UTC
• Commit: 7af60210ff756fa343088d4dc1b7080c200dea50
• Commit Diff: 15ac410...7af6021
• Branch: main

New Dependencies

• Added 11.0.0-preview.3.26176.106
  • Microsoft.Extensions.DependencyInjection.Abstractions

Updated Dependencies

• From 11.0.0-preview.3.26153.117 to 11.0.0-preview.3.26176.106
  • dotnet-dev-certs
  • dotnet-user-jwts
  • dotnet-user-secrets
  • Microsoft.AspNetCore.Analyzers
  • Microsoft.AspNetCore.App.Ref
  • Microsoft.AspNetCore.App.Ref.Internal
  • Microsoft.AspNetCore.Authentication.Facebook
  • Microsoft.AspNetCore.Authentication.Google
  • Microsoft.AspNetCore.Authentication.MicrosoftAccount
  • Microsoft.AspNetCore.Authorization
  • Microsoft.AspNetCore.Components
  • Microsoft.AspNetCore.Components.Analyzers
  • Microsoft.AspNetCore.Components.Forms
  • Microsoft.AspNetCore.Components.SdkAnalyzers
  • Microsoft.AspNetCore.Components.Web
  • Microsoft.AspNetCore.Components.WebAssembly
  • Microsoft.AspNetCore.Components.WebAssembly.Server
  • Microsoft.AspNetCore.Components.WebView
  • Microsoft.AspNetCore.DeveloperCertificates.XPlat
  • Microsoft.AspNetCore.Metadata
  • Microsoft.AspNetCore.Mvc.Analyzers
  • Microsoft.AspNetCore.Mvc.Api.Analyzers
  • Microsoft.AspNetCore.TestHost
  • Microsoft.Bcl.AsyncInterfaces
  • Microsoft.DotNet.Web.ItemTemplates.11.0
  • Microsoft.DotNet.Web.ProjectTemplates.11.0
  • Microsoft.Dotnet.WinForms.ProjectTemplates
  • Microsoft.DotNet.Wpf.ProjectTemplates
  • Microsoft.Extensions.Configuration.Ini
  • Microsoft.Extensions.DependencyModel
  • Microsoft.Extensions.FileProviders.Abstractions
  • Microsoft.Extensions.FileProviders.Embedded
  • Microsoft.Extensions.FileSystemGlobbing
  • Microsoft.Extensions.Logging
  • Microsoft.Extensions.Logging.Abstractions
  • Microsoft.Extensions.Logging.Console
  • Microsoft.Extensions.ObjectPool
  • Microsoft.JSInterop
  • Microsoft.NET.HostModel
  • Microsoft.NET.ILLink.Tasks
  • Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-x64
  • Microsoft.NET.Sdk.WindowsDesktop
  • Microsoft.NETCore.App.Ref
  • Microsoft.NETCore.Platforms
  • Microsoft.Win32.SystemEvents
  • Microsoft.WindowsDesktop.App.Internal
  • Microsoft.WindowsDesktop.App.Ref
  • System.CodeDom
  • System.ComponentModel.Composition
  • System.Composition.AttributedModel
  • System.Composition.Convention
  • System.Composition.Hosting
  • System.Composition.Runtime
  • System.Composition.TypedParts
  • System.Configuration.ConfigurationManager
  • System.Diagnostics.DiagnosticSource
  • System.Formats.Asn1
  • System.IO.Hashing
  • System.Reflection.MetadataLoadContext
  • System.Resources.Extensions
  • System.Security.Cryptography.Pkcs
  • System.Security.Cryptography.ProtectedData
  • System.Security.Cryptography.Xml
  • System.Security.Permissions
  • System.ServiceProcess.ServiceController
  • System.Text.Encoding.CodePages
  • System.Text.Json
  • System.Windows.Extensions
• From 10.0.0-preview.26153.117 to 10.0.0-preview.26176.106
  • Microsoft.AspNetCore.Mvc.Razor.Extensions.Tooling.Internal
  • Microsoft.CodeAnalysis.Razor.Tooling.Internal
  • Microsoft.NET.Sdk.Razor.SourceGenerators.Transport
• From 18.6.0-preview-26153-117 to 18.6.0-preview-26176-106
  • Microsoft.Build
  • Microsoft.Build.Localization
• From 7.5.0-rc.15417 to 7.6.0-rc.17706
  • Microsoft.Build.NuGetSdkResolver
  • NuGet.Build.Tasks
  • NuGet.Build.Tasks.Console
  • NuGet.Build.Tasks.Pack
  • NuGet.CommandLine.XPlat
  • NuGet.Commands
  • NuGet.Common
  • NuGet.Configuration
  • NuGet.Credentials
  • NuGet.DependencyResolver.Core
  • NuGet.Frameworks
  • NuGet.LibraryModel
  • NuGet.Localization
  • NuGet.Packaging
  • NuGet.ProjectModel
  • NuGet.Protocol
  • NuGet.Versioning
• From 11.0.100-preview.3.26153.117 to 11.0.100-preview.3.26176.106
  • Microsoft.Build.Tasks.Git
  • Microsoft.SourceLink.AzureRepos.Git
  • Microsoft.SourceLink.Bitbucket.Git
  • Microsoft.SourceLink.Common
  • Microsoft.SourceLink.GitHub
  • Microsoft.SourceLink.GitLab
  • Microsoft.TemplateEngine.Abstractions
  • Microsoft.TemplateEngine.Authoring.TemplateVerifier
  • Microsoft.TemplateEngine.Edge
  • Microsoft.TemplateEngine.Mocks
  • Microsoft.TemplateEngine.Orchestrator.RunnableProjects
  • Microsoft.TemplateEngine.TestHelper
  • Microsoft.TemplateEngine.Utils
  • Microsoft.TemplateSearch.Common
  • Microsoft.TemplateSearch.TemplateDiscovery
• From 5.6.0-2.26153.117 to 5.6.0-2.26176.106
  • Microsoft.CodeAnalysis
  • Microsoft.CodeAnalysis.BuildClient
  • Microsoft.CodeAnalysis.CSharp
  • Microsoft.CodeAnalysis.CSharp.CodeStyle
  • Microsoft.CodeAnalysis.CSharp.Features
  • Microsoft.CodeAnalysis.CSharp.Workspaces
  • Microsoft.CodeAnalysis.ExternalAccess.HotReload
  • Microsoft.CodeAnalysis.PublicApiAnalyzers
  • Microsoft.CodeAnalysis.Workspaces.Common
  • Microsoft.CodeAnalysis.Workspaces.MSBuild
  • Microsoft.Net.Compilers.Toolset
  • Microsoft.Net.Compilers.Toolset.Framework
• From 2.0.0-preview.1.26153.117 to 2.0.0-preview.1.26176.106
  • Microsoft.Deployment.DotNet.Releases
• From 3.0.0-preview.3.26153.117 to 3.0.0-preview.3.26176.106
  • Microsoft.DiaSymReader
  • System.CommandLine
• From 11.0.0-beta.26153.117 to 11.0.0-beta.26176.106
  • Microsoft.DotNet.Arcade.Sdk
  • Microsoft.DotNet.Build.Tasks.Installers
  • Microsoft.DotNet.Build.Tasks.Templating
  • Microsoft.DotNet.Build.Tasks.Workloads
  • Microsoft.DotNet.Helix.Sdk
  • Microsoft.DotNet.SignTool
  • Microsoft.DotNet.XliffTasks
  • Microsoft.DotNet.XUnitExtensions
• From 15.2.100-preview3.26153.117 to 15.2.100-preview3.26176.106
  • Microsoft.FSharp.Compiler
• From 18.5.0-preview-26153-117 to 18.5.0-preview-26176-106
  • Microsoft.NET.Test.Sdk
  • Microsoft.TestPlatform.Build
  • Microsoft.TestPlatform.CLI
• From 3.3.0-preview.3.26153.117 to 3.3.0-preview.3.26176.106
  • Microsoft.Web.Xdt

Associated changes in source repos

• dotnet/arcade@55c97a4...291fa08
• dotnet/aspnetcore@5f2a8c6...655f41d
• dotnet/command-line-api@a3bae7d...0b720d0
• dotnet/deployment-tools@b94499d...73e2836
• dotnet/efcore@a5a6356...3445554
• dotnet/emsdk@34ea87b...506ea9f
• dotnet/fsharp@1c484e5...1cd0ca0
• dotnet/msbuild@414f0ac...0f7f8dd
• NuGet/NuGet.Client@d2887cd...5e65b14
• dotnet/razor@c4cb27f...d9362b9
• dotnet/roslyn@6bdca1d...675bbbd
• dotnet/runtime@9b46e58...d343974
• 166668d...f25f310
• dotnet/source-build-reference-packages@53df2d8...66ddf29
• dotnet/symreader@df88239...e87544a
• dotnet/templating@fe60e19...a861186
• microsoft/vstest@42e97b7...e315381
• dotnet/winforms@d65e8b0...6735caf

Diff the source with this PR branch

darc vmr diff --name-only https://github.com/dotnet/dotnet:7af60210ff756fa343088d4dc1b7080c200dea50..https://github.com/dotnet/sdk:darc-main-42f55340-3bb4-4b0f-9661-026bcf6564d1

[DonnaChen888]

@MiYanni could you please help take a look at this issue?
error MSB4216: Could not run the "ComputeManagedAssemblies" task because MSBuild could not create or connect to a task host with runtime "NET" and architecture "x64". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "/tmp/helix/working/B2D90971/p/d/sdk/11.0.100-ci/MSBuild" exists and can be run.

[MiYanni]

@dotnet/product-construction We're getting failures on certain runtime MSBuild tasks, such as ComputeManagedAssemblies and ComputeWasmBuildAssets. Not sure what the issue is.
CC @dotnet/runtime-infrastructure

[ViktorHofer]

Looking. Could be due to one my changes. OK: Don't think so.

[dotnet-maestro]

Important

While this PR was open, the source repository has received code changes from this repository (an opposite codeflow merged).
To avoid complex conflicts, the codeflow cannot continue until this PR is closed or merged.

You can continue with one of the following options:

• Ignore this and merge this PR as usual without waiting for the new changes.
  Once merged, Maestro will create a new codeflow PR with the new changes.
• Close this PR and wait for Maestro to open a new one with old and new changes included.
  You will lose any manual changes made in this PR.
  You can also manually trigger the new codeflow right away by running:

  darc trigger-subscriptions --id 94ba9a9b-a084-4c1e-bf44-d0c711c17773
  

• Force a codeflow into this PR at your own risk if you want the new changes.
  User commits made to this PR might be reverted.

  darc trigger-subscriptions --id 94ba9a9b-a084-4c1e-bf44-d0c711c17773 --force
  

💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance.

[ViktorHofer]

@dotnet/dotnet-cli the remaining failure seem to be non-msbuild related. Explicit hand-off :)

[nagilson]

Error 1: The blazor test project doesn't build because of this: An item with the same key has already been added. I think we've seen this before. @dotnet/aspnet-blazor-eng May you PTAL?

C:\h\w\AAFF0945\p\d\sdk\11.0.100-ci\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets(297,5): error MSB4018: The "DiscoverPrecompressedAssets" task failed unexpectedly. [C:\h\w\AAFF0945\t\dotnetSdkTests\jv4vxzyu.ynl\Publish_Hosti---AC2D7A92\BlazorMultipleApps.Server\BlazorMultipleApps.Server.csproj]
C:\h\w\AAFF0945\p\d\sdk\11.0.100-ci\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets(297,5): error MSB4018: System.ArgumentException: An item with the same key has already been added. [C:\h\w\AAFF0945\t\dotnetSdkTests\jv4vxzyu.ynl\Publish_Hosti---AC2D7A92\BlazorMultipleApps.Server\BlazorMultipleApps.Server.csproj]

Error 2: Template engine legacy behavior test failure:
Assert.Contains() Failure: Filter not matched in collection\r\nCollection: [Required argument 'package' missing for command: 'install'.] in both Install_Legacy_Error_NoArguments and Install_Error_NoArguments

Looking into #2... whether we changed the behavior and if this is expected or not.

[YuliiaKovalova]

Error 1: The blazor test project doesn't build because of this: An item with the same key has already been added. I think we've seen this before. @dotnet/aspnet-blazor-eng May you PTAL?

C:\h\w\AAFF0945\p\d\sdk\11.0.100-ci\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets(297,5): error MSB4018: The "DiscoverPrecompressedAssets" task failed unexpectedly. [C:\h\w\AAFF0945\t\dotnetSdkTests\jv4vxzyu.ynl\Publish_Hosti---AC2D7A92\BlazorMultipleApps.Server\BlazorMultipleApps.Server.csproj]
C:\h\w\AAFF0945\p\d\sdk\11.0.100-ci\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets(297,5): error MSB4018: System.ArgumentException: An item with the same key has already been added. [C:\h\w\AAFF0945\t\dotnetSdkTests\jv4vxzyu.ynl\Publish_Hosti---AC2D7A92\BlazorMultipleApps.Server\BlazorMultipleApps.Server.csproj]

Error 2: Template engine legacy behavior test failure: Assert.Contains() Failure: Filter not matched in collection\r\nCollection: [Required argument 'package' missing for command: 'install'.] in both Install_Legacy_Error_NoArguments and Install_Error_NoArguments

Looking into #2... whether we changed the behavior and if this is expected or not.

I was looking at it with @matouskozak today, the root cause seems to be coming from Initial migration work · dotnet/templating@2070dc7

It might be it:

https://github.com/dotnet/templating/blob/953ad16c40b654e89098bb504561e258c7890f28/src/Shared/JExte…

in the previous json package it was automatically overwritten, but now it fails due to different implementation in System.Text.Json https://github.com/dotnet/runtime/blob/baa4920c39cbd92a5704218d11a1d6648950b6f5/src/libraries/Syste…

In maui it manifests in dotnet/templating#10025

https://github.com/dotnet/maui/blob/b4dad751906e865863bdf05a9f7f38b4cee0b552/src/Templates/src/temp…

[nagilson]

I certainly think that's possible, thank you for that thoughtful investigation. I'm wondering if it was the behavioral change in output due to dotnet/command-line-api#2747 as well though.

[nagilson]

@javiercn Please look at the blazor failure I mentioned in #53350 (comment), I think d28b5e32499#diff-607f4c722217861f4222bc59d983d008773cbec9c7330462f9dcf406cf639d79 ToDictionary() throws "An item with the same key has already been added" when multiple Blazor WASM client projects
(like in BlazorMultipleApps) reference the same NuGet runtime pack files and we should use a dictionary construction which allows identical identity values. But this is surface level.

[dotnet-policy-service]

Thanks for your PR, @@dotnet-maestro[bot].
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

[nagilson]

The template engine issue is fixed, we're just waiting for the blazor fix. I'll ping outside of teams and merge on red/flag the blazor tests as 'known' tomorrow for code complete if it's not fixed then.

[nagilson]

I can confirm dotnet/runtime#125329 the runtime is working on a fix for this. Marking as known issue.

[lewing]

dotnet/runtime#125329 finally has the flow it needs and once it merges, flows to the vrmr then backflows to sdk things should work. If you do open an known build error just don't leave it open indefinitely

[nagilson]

@YuliiaKovalova ea761e0 Should this have been reverted? The msbuild break from earlier appears to be back now that this is reverted. I'll try adding it back as it seemed to make things pass on my machine.

[YuliiaKovalova]

@YuliiaKovalova ea761e0 Should this have been reverted? The msbuild break from earlier appears to be back now that this is reverted. I'll try adding it back as it seemed to make things pass on my machine.

I think it's not needed, once we pull latest changes from dotnet/dotnet (I need msbuild with this commit dotnet/msbuild#13406). Can we do it to check?

[YuliiaKovalova]

@YuliiaKovalova ea761e0 Should this have been reverted? The msbuild break from earlier appears to be back now that this is reverted. I'll try adding it back as it seemed to make things pass on my machine.

yes, this change isn't needed - after getting the necessary change in #53510 the failure went away.

[nagilson]

@YuliiaKovalova ea761e0 Should this have been reverted? The msbuild break from earlier appears to be back now that this is reverted. I'll try adding it back as it seemed to make things pass on my machine.

yes, this change isn't needed - after getting the necessary change in #53510 the failure went away.

I believe we hit the failure again in the last run still on Mac OS, demonstrated one time EndToEnd.Tests.ProjectBuildTests.EndToEnd.Tests.ProjectBuildTests.ItCanCreateAndBuildTemplatesWithDefaultFramework(templateName: "blazorwasm", language: "") :

/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/.nuget/packages/microsoft.net.sdk.webassembly.pack/11.0.0-preview.3.26161.119/build/Microsoft.NET.Sdk.WebAssembly.Browser.targets(325,5): error MSB4216: Could not run the "ComputeWasmBuildAssets" task because MSBuild could not create or connect to a task host with runtime "NET" and architecture "x64".  Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "/tmp/helix/working/B74A099B/p/d/sdk/11.0.100-ci/MSBuild" exists and can be run. [/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/InstantiatePr---8021C1A8/InstantiatePr---8021C1A8.csproj]
/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/.nuget/packages/microsoft.net.sdk.webassembly.pack/11.0.0-preview.3.26161.119/build/Microsoft.NET.Sdk.WebAssembly.Browser.targets(344,7): error MSB4027: The "ComputeWasmBuildAssets" task generated invalid items from the "AssetCandidates" output parameter. This object is no longer valid because the MetadataLoadContext that created it has been disposed. [/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/InstantiatePr---8021C1A8/InstantiatePr---8021C1A8.csproj]
0 Warning(s)

Now, it could be due to me adding back your change (?) so I'll revert the revert. But, I'm also wondering if it's not completely fixed? I saw it the last time before that was added as well. What do you think @YuliiaKovalova?

[lewing]

dotnet/runtime#125329 finally has the flow it needs and once it merges, flows to the vrmr then backflows to sdk things should work. If you do open an known build error just don't leave it open indefinitely

The vmr is flowing with the prospective fix now so once you can take new flow the multiple wasm project thing should be fixed. There might be baseline changes that come with it, I will keep an eye out but feel free to ping me directly.

[YuliiaKovalova]

@YuliiaKovalova ea761e0 Should this have been reverted? The msbuild break from earlier appears to be back now that this is reverted. I'll try adding it back as it seemed to make things pass on my machine.

yes, this change isn't needed - after getting the necessary change in #53510 the failure went away.

I believe we hit the failure again in the last run still on Mac OS, demonstrated one time EndToEnd.Tests.ProjectBuildTests.EndToEnd.Tests.ProjectBuildTests.ItCanCreateAndBuildTemplatesWithDefaultFramework(templateName: "blazorwasm", language: "") :

/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/.nuget/packages/microsoft.net.sdk.webassembly.pack/11.0.0-preview.3.26161.119/build/Microsoft.NET.Sdk.WebAssembly.Browser.targets(325,5): error MSB4216: Could not run the "ComputeWasmBuildAssets" task because MSBuild could not create or connect to a task host with runtime "NET" and architecture "x64".  Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "/tmp/helix/working/B74A099B/p/d/sdk/11.0.100-ci/MSBuild" exists and can be run. [/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/InstantiatePr---8021C1A8/InstantiatePr---8021C1A8.csproj]
/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/.nuget/packages/microsoft.net.sdk.webassembly.pack/11.0.0-preview.3.26161.119/build/Microsoft.NET.Sdk.WebAssembly.Browser.targets(344,7): error MSB4027: The "ComputeWasmBuildAssets" task generated invalid items from the "AssetCandidates" output parameter. This object is no longer valid because the MetadataLoadContext that created it has been disposed. [/private/tmp/helix/working/B74A099B/t/dotnetSdkTests.G5gTHifL/InstantiatePr---8021C1A8/InstantiatePr---8021C1A8.csproj]
0 Warning(s)

Now, it could be due to me adding back your change (?) so I'll revert the revert. But, I'm also wondering if it's not completely fixed? I saw it the last time before that was added as well. What do you think @YuliiaKovalova?

@nagilson , I don't see the latest changes from dotnet/dotnet with msbuild in it

can we pull changes from main dotnet/dotnet?

[dotnet-maestro]

Caution

🛑 Codeflow Paused — Conflict detected

A conflict was detected when trying to update this PR with changes from build 307929 of https://github.com/dotnet/dotnet/tree/7af60210ff756fa343088d4dc1b7080c200dea50.

💡 You can either merge the PR without getting these new updates or manually flow them in and resolve the conflicts so that automated codeflow can resume for this PR.

The conflicts in the following files need to be manually resolved:

• test/Microsoft.TemplateEngine.Cli.UnitTests/TemplatePackageCoordinatorTests.cs
  🔍 View file in dotnet/sdk vs VMR

ℹ️ To resolve the conflicts, please follow these steps:

1. Clone the current repository

   git clone https://github.com/dotnet/sdk
   cd sdk

2. Make sure your darc is up-to-date
   (version 1.1.0-beta.26176.1 or higher)

   # Linux / MacOS
   ./eng/common/darc-init.sh
   # or on Windows
   .\eng\common\darc-init.ps1

3. Run from repo's git clone and follow the instructions provided by the command to stage the conflict locally

   darc vmr resolve-conflict --subscription 94ba9a9b-a084-4c1e-bf44-d0c711c17773

   This should apply the build 307929 with sources from 7af6021
4. Resolve the conflicts, commit & push the changes
5. Once pushed, the Codeflow verification check will turn green.
   If not, a new build might have flown into the PR and you might need to run the command above again.

💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance.

[akoeplinger]

as mentioned in #53350 (comment) the automatic codeflow into this PR has stopped due to an opposite codeflow.

I force-triggered the subscription but there's a chance it will mess something up. If that happens we need to close this PR and trigger a new one and then cherry-pick the manual commits over there.

[akoeplinger]

ok yeah let's not try to resolve the conflict here.

[akoeplinger]

new PR: #53613