.NET Hot Reload Support via CLI

Re:.NET Hot Reload Support via CLI by gbraad on Saturday October 23, 2021 @09:36PM (#28974115)

You can use OmniSharp. It is not ideal, but makes life easier.

Though it seems MS actively disallows employees to come n tribute to them.

If you do GUI work, you pretty much have to use VS. :-/

[ Parent | on HN ]

Re:.NET Hot Reload Support via CLI by DeathArrow on Sunday October 24, 2021 @03:25AM (#28975636)

Intellisense is not that good. Intellicode is missing. Managing nugget packages is not so well integrated. It's harder to debug and investigate memory leaks. I can't see code coverage in the editor or run tests with right click straight from the method I want to test.

It's usable for sure but the development it's not as fast as in Visual Studio.

I still use VS Code if I want to modify some files like XML, json, yaml, and I don't want to fire another instance of Visual Studio for that.

[ Parent | on HN ]

Re:.NET Hot Reload Support via CLI by rafaelvasco on Sunday October 24, 2021 @12:13AM (#28974911)

VS used to be heavy and bloated. But that was a long time ago. I use VS since 2010 version. It improved by leaps and bounds since then. New 2022 version is almost as fast as VSCode, if you have a good PC.

[ Parent | on HN ]

Re:.NET Hot Reload Support via CLI by babypuncher on Friday November 05, 2021 @11:52PM (#29127365)

Microsoft's official C#/.NET extensions for VS Code use OmniSharp to provide IntelliSense, so I think they are becoming a lot more friendly on that front.

As others have already pointed out, OmniSharp is "good enough", but what's built into Visual Studio is still a lot better.

[ Parent | on HN ]