Microsoft returned the Hot Reload code to the .NET repository

Microsoft listened to the opinion of the community and returned to the .NET SDK repository the code with the implementation of the "Hot Reload" function, which was removed from the codebase a few days ago, despite the fact that it was already considered open and was part of the preliminary releases of .NET 6. Company representatives apologized to the community and admitted that they made a mistake by removing the already added code and not immediately responding to the community's dissatisfaction. It is also stated that the company continues to position .NET as an open platform and will continue to develop it in accordance with the open development model.

It is explained that due to lack of resources and time before the release of .NET 6, it was decided to offer Hot Reload only in Visual Studio 2022, but the main mistake was that instead of simply not activating the code already added to the open codebase, this code has been removed from the repository. Mentioning the lack of resources to bring "Hot Reload" to the final release of .NET 6 raises questions, since this feature was already included in the final text releases of .NET 6 RC1 and .NET 6 RC2, and was tested by users. Developing in Visual Studio 2022 also doesn't provide additional development time, as Visual Studio 2022 and .NET 6 releases are scheduled for the same day, November 8th.

Leaving "Hot Reload" only in the commercial product Visual Studio 2022 was originally supposed to increase its competitive appeal compared to free development tools. According to The Verge, the removal of the "Hot Reload" code was a management decision made by Julia Liuson, head of Microsoft's product development division.

Recall that the Hot Reload feature provides a means to edit code on the fly while the program is running, allowing you to make changes without manually stopping execution and without attaching breakpoints. The developer could run the application under dotnet watch, after which the changes made to the code were automatically applied to the running application, which made it possible to immediately observe the result.

Source: opennet.ru

Add a comment