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
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).
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.
Comments
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
I can imagine doing such a thing to cut off inevitable noise.
Have any other open source / free software packages locked down a PR?
Un-editorialized title: “Update on .NET Hot Reload progress and Visual Studio 2022 Highlights”
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).
The "Unsupported Scenarios" is interesting, is this a sign Xamarin and F# are on the way out?
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.
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.