That feature is part of the Hot Reload component of .NET that Microsoft. Specifically, Microsoft was removing an ability for developers to receive real-time feedback when changing code. It essentially brought the ability to change code when needed. Microsoft said last week that .NET 6 will remove this ability. Hot Reload gives developers on .NET and native C++ apps the ability to boost productivity during the build process of their applications. Microsoft said last week it would not bring Hot Reload to .NET, instead keeping it as an exclusive on Visual Studio: The company announced it “will enable Hot Reload functionality only through Visual Studio 2022 so we can focus on providing the best experiences to the most users.”

Response

Many in the open source community were angered by Microsoft’s decision. After a decade of cultivating a relationship with open source, this felt like a step back. With widespread criticism, it is perhaps no surprise that Microsoft quickly went into damage limitation mode and reversed its decision. Within a day, the company was back with a change of heart. Speaking to The Verge, the company says Hot Reload will come to .NET 6 on November 6 on November 8 after-all: “We have taken steps to address the issue that some of our OSS community members have experienced,” says a Microsoft spokesperson says. “Hot Reload capability will be in the general availability build of the .NET 6 SDK available on November 8th.” Microsoft also published a blog post highlighting its decision. Tip of the day: Tired of Windows 10’s default notification and other system sounds? In our tutorial we show you how to change windows sounds or turn off system sounds entirely.

Microsoft Reverses Controversial Decision to Remove Hot Reload from  NET 6 - 42Microsoft Reverses Controversial Decision to Remove Hot Reload from  NET 6 - 58Microsoft Reverses Controversial Decision to Remove Hot Reload from  NET 6 - 56Microsoft Reverses Controversial Decision to Remove Hot Reload from  NET 6 - 95