[automated] Merge branch 'main' => 'release/dnup'

[github-actions]

I detected changes in the main branch which have not been merged yet to release/dnup. I'm a robot and am configured to help you automatically keep release/dnup up to date, so I've opened this PR.

This PR merges commits made on main by the following committers:

• MichaelSimons
• nagilson
• dsplaisted
• SimaTian
• baronfel

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout main
git pull --ff-only
git checkout release/dnup
git pull --ff-only
git merge --no-ff main

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet/sdk HEAD:merge/main-to-release/dnup

or if you are using SSH

git push git@github.com:dotnet/sdk HEAD:merge/main-to-release/dnup

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/main-to-release/dnup'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.

git fetch
git checkout -b merge/main-to-release/dnup origin/release/dnup
git pull https://github.com/dotnet/sdk merge/main-to-release/dnup
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/sdk HEAD:merge/main-to-release/dnup

or if you are using SSH

git fetch
git checkout -b merge/main-to-release/dnup origin/release/dnup
git pull git@github.com:dotnet/sdk merge/main-to-release/dnup
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/sdk HEAD:merge/main-to-release/dnup

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

[DonnaChen888]

/azp run dotnet-sdk-public-ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[DonnaChen888]

@joeloff could you please help me to take a look at this issue?
C:\Program Files\Microsoft Visual Studio\18\Insiders\Common7\IDE\CommonExtensions\Microsoft\NuGet\NuGet.targets(196,5): error : '10.0.' is not a valid version string.

[MiYanni]

@dotnet/dotnetup There are some test failures here. One of them is the aforementioned 10.0 issue. Another is:

C:\h\w\AAAC094D\p\d\sdk\11.0.200-ci\Sdks\Microsoft.NET.Sdk.BlazorWebAssembly\targets\Microsoft.NET.Sdk.BlazorWebAssembly.5_0.targets(650,5): error : The process cannot access the file 'C:\h\w\AAAC094D\t\dotnetSdkTests\th1wxmo0.wwy\StaticWebAsse---CC4E9A05\blazorwasm\obj\Debug\net5\compress\2OdDz7lN.gz' because it is being used by another process. [C:\h\w\AAAC094D\t\dotnetSdkTests\th1wxmo0.wwy\StaticWebAsse---CC4E9A05\blazorwasm\blazorwasm.csproj]

Another is:

Microsoft.DotNet.Watch.UnitTests.ApplyDeltaTests.ProjectChange_Update(isDirectoryProps: False) [OUTPUT] dotnet watch ⚠ msbuild: [Failure] Cannot open project 'C:\h\w\AAAC094D\t\dotnetSdkTests\axneu5rr.mfz\ProjectChange---0B95B003\FSharp\Lib.fsproj' because the file extension '.fsproj' is not associated with a language.

Not sure if any of these are related to the changes. Also, should all the SDK jobs be running on the release/dnup branch like this?

[nagilson]

@dotnet/dotnetup There are some test failures here. One of them is the aforementioned 10.0 issue. Another is:
Also, should all the SDK jobs be running on the release/dnup branch like this?

The SDK tests run if and only if there's a change in the source code to the SDK branch. Sometimes we change the SDK source code for dotnetup a bit, so this is intentional.