Move away from unsupported version of .NET Framework #30968
Closed
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
|
Note, we're not running on this version; we're just compiling against its APIs. Users are responsible for upgrading to a supported version of the runtime. This would be a pretty significant breaking change. |
This used to work via the Microsoft.NETFramework.ReferenceAssemblies NuGet package instead, but something changed. |
|
Note from trigae: this is not something we are going to merge right now. Figuring out why Microsoft.NETFramework.ReferenceAssemblies doesn't work is a reasonable MQ task. |
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.
.NET Framework v4.6.1 was retired in April 2022. A year has already passed, so users have clearly had enough time to update. This also eliminates the need of installing legacy .NET Framework developer pack in VS