.NET Hot Reload Support via CLI
devblogs.microsoft.com
devblogs.microsoft.com
From the post:
> "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 on this plan in the way it was carried out. In our effort to scope, we inadvertently ended up deleting the source code instead of just not invoking that code path."
Everyone commenting “Microsoft, why? You suck!” doesn’t add to the discussion.
> “In our effort to scope, we inadvertently ended up deleting the source code instead of just not invoking that code path."
I’m not sure the original blog post announcing the drop of this feature was completely transparent, and similarly I’m not sure that this retraction post is either. There’s too much additional context that points to a slightly different explanation.
But at least they back tracked. That’s a win.