Last Updated on 22/11/2021 by Sanskriti
Earlier week Microsoft enraged the.NET open-source community by eliminating a crucial feature of Hot Reload from the impending release of.NET 6, a feature that allows developers to make changes to source code while an app is running and see the effects instantly. Following a public uproar from the open-source community, Microsoft has now reversed its plan to remove a critical feature from its upcoming.NET 6 versions.
As a result of their previous doing, Microsoft has received a strong backlash for deleting an essential feature, and for that Microsoft issued an apology to the open-source community. Microsoft has recently “approved the pull request” to re-enable this code path, which will be included in the.NET 6 SDK’s general availability version.
Microsoft had previously opted to confine the ‘Hot Reload functionality’ to Visual Studio 2022, which is only available for Windows and costs money. According to The Verge, Microsoft’s president of developer division Julia Liuson made the decision to eliminate this functionality as a “business-focused move.”
Microsoft said after reversing the decision to remove ‘Hot Reload Capability’,
“First and foremost, we want to apologize. We made a mistake in executing our decision and took longer than expected to respond back to the community.”
“With the runway getting short for the .NET 6 release and Visual Studio 2022, we chose to focus on bringing Hot Reload to VS2022 first. We made a mistake in executing this plan in the way it was carried out.”
“We inadvertently ended up deleting the source code instead of just not invoking that code path. We underestimated the number of developers that are dependent upon this capability,” Microsoft said in a blogpost in their defense.
Although the firm has taken back its decision and will be welcomed by the.NET community, individuals who value transparency in such choices will be disappointed by the reasoning and circumstances surrounding this episode.