[Windows] Move .NET 7.0 to the toolset due to the new Visual Studio version #8798
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Alexey-Ayupov
force-pushed
the
windows-update-dotnet
branch
from
fa446d0 to
6de98b3
Compare
|
/azp run windows2019,windows2022 |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
If the change is specific to VS 17.8, shouldn't it only be for the windows20222 image? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Move .NET 7.0 to the toolset due to the new Visual Studio version
Related issue:
#8797
Check list