[automated] Merge branch 'vs17.14' => 'vs18.0'

[github-actions]

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

This PR merges commits made on vs17.14 by the following committers:

• @AlesProkop
• @dotnet-maestro[bot]

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 vs17.14
git pull --ff-only
git checkout vs18.0
git pull --ff-only
git merge --no-ff vs17.14

# 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/msbuild HEAD:merge/vs17.14-to-vs18.0

or if you are using SSH

git push git@github.com:dotnet/msbuild HEAD:merge/vs17.14-to-vs18.0

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/vs17.14-to-vs18.0'. 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/vs17.14-to-vs18.0 origin/vs18.0
git pull https://github.com/dotnet/msbuild merge/vs17.14-to-vs18.0
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/msbuild HEAD:merge/vs17.14-to-vs18.0

or if you are using SSH

git fetch
git checkout -b merge/vs17.14-to-vs18.0 origin/vs18.0
git pull git@github.com:dotnet/msbuild merge/vs17.14-to-vs18.0
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/msbuild HEAD:merge/vs17.14-to-vs18.0

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.

[github-actions]

This pull request has been updated.

This PR merges commits made on vs17.14 by the following committers:

• @JanProvaznik
• @AlesProkop
• @dotnet-maestro[bot]

[ViktorHofer]

@rainersigwald please take a look at these failures. I'm a bit confused on what versions we want here for vs18.0 vs what NuGet dependencies bring in. This is due to 25f168c flowing forward.

[rainersigwald]

I don't think we need to preserve any of the complexity from 17.14 here, which enabled a much easier way to resolve the conflicts: don't. That is,

❯ git reset --hard origin/vs18.0
HEAD is now at fa030cda17 [vs18.0] Update dependencies from dotnet/arcade (#13984)

❯ git merge -s ours --no-ff --no-commit origin/vs17.14
Automatic merge went well; stopped before committing as requested

❯ git cherry-pick -n fe00274ead
Auto-merging eng/Versions.props

❯ git commit -m "Merge branch 'vs17.14' into 'vs18.0'"
[merge/vs17.14-to-vs18.0 46d46aa98b] Merge branch 'vs17.14' into 'vs18.0'

[ViktorHofer]

Interesting. Why don't we need 25f168c in 18.0? Isn't it weird to not have 10.0.x binding redirects and runtime assemblies there when they are present in 17.14?