In this edition: yet another week filled with .NET drama, this time involving the brand new Hot Reload feature in .NET 6.
Take your seats please! The show is about to begin. Photo by Annie Gavin / Unsplash
Plus: a breakdown of the OWASP Top Ten; explaining C# compiler errors; VS 2022's visual refresh; creating a search engine; and Space Cadet Pinball returns from the dead!
More .NET Drama with Hot Reload
On October 20th, Microsoft released a blog post all about the new Hot Reload feature available in .NET 6 and how Visual Studio 2022 could be used with it.
Buried in that post was a particular sentence that set off yet another wave of .NET drama:
"With these considerations, we’ve decided that starting with the upcoming .NET 6 GA release, we will enable Hot Reload functionality only through Visual Studio 2022 so we can focus on providing the best experiences to the most users."
Yep, Microsoft announced that Hot Reload, one of its most requested features, would only be available in Visual Studio 2022. Meaning that people write .NET code using JetBrains Rider or other IDEs would be out of luck.
As you might imagine, the community revolted:
This hot reload change seems like a really misguided decision on the part of Microsoft. https://t.co/LnwlgHsH2P I develop .NET on a Mac, but deploy all my software to Azure. I do not like feeling like an afterthought to my development platform. Some background...
Microsoft pulling hot reload shouldn't come as a shock to anyone. Years ago they changed the OSS license of some debugging packages to only allow it to be used by their own tools. We (@JetBrainsRider) ended up writing our own debugger, just like we have for hot reload.
Whether or not this was a business decision or some other kind, I have no idea. From the outside, it looks like MS was wanting to promote the usage of one of its flagship products.
However, just a couple days ago (and one day after The Verge published the above article), MS reversed course and added back Hot Reload to .NET 6 as a native feature:
