Revenge of the donkey
Microsoft removes hot reload from open source .NET, locks it to Visual Studio
11–20 of 62 posts
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#12I'm the author of that issue. I think I can be a little more frank here: this is a horrifically short-sighted decision that has me scared for the future of .NET. I have a tremendous amount of respect for the .NET team, and I'm very certain they're not the ones behind this. I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple…
Visual studio is anything but legacy and I haven't found anything better. Where does the future lie?
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#13I'm the author of that issue. I think I can be a little more frank here: this is a horrifically short-sighted decision that has me scared for the future of .NET. I have a tremendous amount of respect for the .NET team, and I'm very certain they're not the ones behind this. I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple…
Visual studio is anything but legacy and I haven't found anything better. Where does the future lie?
VS is great for desktop apps since it has the designer and some other tooling, but for everything else Rider is miles ahead, in my opinion.
Especially when it comes to web. Visual Studio still dies of stroke as soon as someone dares whisper the word "razor" in its vicinity, while Rider has no problem understanding Razor templates and providing full autocompletion.
Not to mention Rider is just straight out snappier. And has integrated terminal without any need for extensions.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#14Welcome to corporate-owned open-source. You COULD fork .NET and add hot-reload back in. But you won't. And they know it.
I wonder how hard to diff the feature back in.
It's, apparently, a couple thousands lines. It could, perhaps, even be made into its own separate tool. Haven't looked at it myself, though.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#15I'm the author of that issue. I think I can be a little more frank here: this is a horrifically short-sighted decision that has me scared for the future of .NET. I have a tremendous amount of respect for the .NET team, and I'm very certain they're not the ones behind this. I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple…
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.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#16Extend. So you can't use this feature on Jetbrains Rider or any other app other than Visual Studio. This is typical Microsoft, so it's unsurprising. But they have a strange way of 'embracing' open source.
It’s their own code. You’re accusing Microsoft of EEEing their own code?
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#17I'm the author of that issue. I think I can be a little more frank here: this is a horrifically short-sighted decision that has me scared for the future of .NET. I have a tremendous amount of respect for the .NET team, and I'm very certain they're not the ones behind this. I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple…
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.
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.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#18.NET is one of those languages you want to give a chance, and every time you do, it does something incredibly short sighted and harmful to itself.
You just can't change Microsoft. You can put fancy new skins on things and say you're part of the cool kids, but remember the people who made all of Microsoft s terrible moments aren't the young devs that care. It's management.
The only way I will ever use .net is if an actual open source implementation detached from MS happens. Openjdk it.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#19.NET is one of those languages you want to give a chance, and every time you do, it does something incredibly short sighted and harmful to itself. You just can't change Microsoft. You can put fancy new skins on things and say you're part of the cool kids, but remember the people who made all of Microsoft s terrible moments aren't the young devs that care. It's management. The only way I will ever use .net is if an ac…
There's already Mono.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#20Earlier quoted context omitted.
Visual studio is anything but legacy and I haven't found anything better. Where does the future lie?
VS is great for desktop apps since it has the designer and some other tooling, but for everything else Rider is miles ahead, in my opinion. Especially when it comes to web. Visual Studio still dies of stroke as soon as someone dares whisper the word "razor" in its vicinity, while Rider has no problem understanding Razor templates and providing full autocompletion. Not to mention Rider is just straight out snappier. A…
Unfortunately, I need SQL Project support before I can ever consider switching to Rider. I could almost move to VSCode for everything but MS refuses to implement nested files. Currently I do prefer writing C# in VS though.