[deburo]

I understand the huge disappointment but there’s a bit of hyperbole there. Anyway, lets hope they reconsider w/ .net 7. At the pace they’re going, in a years time.

[ripley12]

Not hyperbole.

If .NET is going to stay relevant in the long run, it needs a better reputation for cross-platform development and much better tooling outside of Visual Studio. Newcomers to the language expect it to work well in VS Code, and they are frequently disappointed.

This decision moves .NET backward in areas it already needs to do better in, and to add insult to injury it does so by deleting already-working code.

[deburo]

It's disappointing that they want it to be exclusive to VS (that giant turtle) right now, but it's a new Hot Reload feature. For most existing .NET devs, it's business as usual.

It may set a trend in which VS is pushed as the tool of choice to develop in .NET, which would be a total bummer. I'm a bit skeptical about this since they would be damaging their huge investment in VSCode and cmdline tools. As far as I know, Azure is still their priority. What happened to their leadership to cause such a reversal? Pressure to sell more VS licenses? Maybe, but it still seems doubtful.

I'm giving them the benefit of the doubt until they either explain themselves better, or they release .NET 7 without any goodies to the cmdline devs.

[tluyben2]

As someone who has put the future of my company on .net core this is not hyperbole; this is quite a worrying development. I did not pick Java because .net core has served me well when I build some prototypes 5 years ago (the 15 years before that we did mostly but I sold that company and all my colleagues were tied in the sale, willingly so I could re evaluate tech).