Microsoft locks .NET hot reload capabilities behind Visual Studio 2022

https://devblogs.microsoft.com/dotnet/update-on-net-hot-reload-progress-and-visual-studio-2022-highlights/

by Angius • 5 years ago

10 7 5 years ago

devblogs.microsoft.com

Angius• 5 years ago

What's curious, is that the PR that introduces this change is the only PR on the repo that has discussion limited to collaborators only: https://github.com/dotnet/sdk/pull/22217

WalterGR2• 5 years ago

I can imagine doing such a thing to cut off inevitable noise.

Have any other open source / free software packages locked down a PR?

WalterGR2• 5 years ago

Un-editorialized title: “Update on .NET Hot Reload progress and Visual Studio 2022 Highlights”

cube00• 5 years ago

The "Unsupported Scenarios" is interesting, is this a sign Xamarin and F# are on the way out?

HappySweeney• 5 years ago

Xamarin is being subsumed and F# just got a new version with stuff to make it easier on beginners, so I doubt they will drop it anytime soon.

lostmsu• 5 years ago

F# compiler architecture might simply not be suitable. It started as a research project, and its code quality shows that. I don't think Visual Studio ever supported edit-and-continue for F#. Live reload seems to be an upgraded version of that feature.

moogly• 5 years ago

Editorialized headline, but it is disappointing. The feature is misnamed since it's a VS feature and not a feature for the entire .NET ecosystem (including VS Code).

Microsoft locks .NET hot reload capabilities behind Visual Studio 2022

Related Stories