Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move away from unsupported version of .NET Framework #30968

Closed
wants to merge 1 commit into from
Closed

Move away from unsupported version of .NET Framework #30968

wants to merge 1 commit into from

Conversation

DoctorKrolic
Copy link
Contributor

.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

@bricelam
Copy link
Contributor

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.

@bricelam
Copy link
Contributor

This also eliminates the need of installing legacy .NET Framework developer pack in VS

This used to work via the Microsoft.NETFramework.ReferenceAssemblies NuGet package instead, but something changed.

@ajcvickers
Copy link
Member

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.

@ajcvickers ajcvickers closed this Jun 4, 2023
@DoctorKrolic DoctorKrolic deleted the retire-old-framework branch June 4, 2023 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants