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.
Related Issue
Fixes #6455
Description
This probably warrants a longer explanation, but the short of it is that the latest VS tools release breaks some Nuget tooling in some specific scenarios (that unfortunately apply to us). This appears to only have affected the
.NET Core 3.xSDK tooling..NET 5(basically the latest version of .NET Core - ask me for a .NET versioning rant sometime) is sufficiently different such that it's apparently unaffected. This change moves our .NET Core projects over to.NET 5. I've already updated the build pipeline to pull the5.xSDK. It's worth calling out that the updated projects don't impact our platform packages (just tests and the visualizer).Microsoft Reviewers: Open in CodeFlow