After apologizing for inadvertently removing the Hot Reload hot code modification feature in the .NET 6 SDK repository, Microsoft rolled back.
In the face of strong dissatisfaction in the open source community over the removal of the Hot Reload feature from the .NET SDK repository, Microsoft has backed down. In a blog post on October 23 regarding support for the .NET framework’s Hot Reload hot-code modification feature through the CLI, Scott Hunter, director of program management for .NET, s I apologize for this deletion. “We made a mistake in implementing our decision and took longer than expected to respond to the community. We have approved the request to reactivate this code path and it will be incorporated into the generally available version of the .NET 6 SDK, ”he said.
Hot Reload allows developers to modify the managed source code of a running application, without the need to pause it or activate a breakpoint. Previewed in Visual Studio 2019, the full feature experience will normally be available in the production version of Visual Studio 2022, which is slated for release on November 8. Microsoft’s .NET 6 software development platform is also expected on this date. Mr Hunter said that due to the lack of time until the release date of the .NET 6 release and Visual Studio 2022, Microsoft has chosen to focus on integrating Hot Reload with Visual first. Studio 2022.
Provide a better experience for. NET 6
Mr. Hunter admitted that Microsoft “had underestimated the number of developers who depended on this capability in their environments and in their scenarios, and also underestimated the use by many developers of the CLI with Visual Studio to optimize productivity. of the internal development loop ”. He also said that the vast majority of .NET developers use Visual Studio and that Microsoft wants to make sure that the IDE provides the best experience for .NET 6.
On October 20, Microsoft blogged about the progress of Hot Reload and Visual Studio 2022, touting the use of Hot Reload with Visual Studio 2022. The blog also mentioned unsupported scenarios for Hot Reload, including applications built using F # or those targeting .NET Native.