4 ms·
Honestly, unless I'm working on a Windows machine, I find JetBrains Rider to be the best option for C# specifically. This is especially true if you like having
by twodave 6y ago
Honestly, unless I'm working on a Windows machine, I find JetBrains Rider to be the best option for C# specifically. This is especially true if you like having your tests easily accessible from your IDE.
That said, VSCode is still very nice for front-end pretty much universally, and it's also great for things like back-end Javascript/Typescript. I think Codespaces is really going to excel when it comes to things like NodeJS -> AWS Lambda. Make code changes, run "sls test", done.
- recursive 6y ago> This is especially true if you like having your tests easily accessible from your IDE. I haven't used Rider, but I'm curious how it could be easier than the Visual Studio test explorer? It seems pretty convenient, and doesn't lack any obvious features I can think of.
- noworriesnate 6y agoMinor point: the Rider test explorer tells you why your tests aren't appearing. Visual Studio's test explorer will just say "You have no tests, try rebuilding your solution" even if you already rebuilt it.
- peteri 6y agoI assume in part this is because the Rider test explorer is based on the one in Resharper. Some stuff it does better is things like running 64 bit and 32 bit tests at the same time, supporting both nUnit 2 & 3 without having to disable/enable the plugin. Mind you I spent some time with code in release mode trying to work why I couldn't debug a test last week. To be fair I hate what Resharper does for Visual Studio performance and a lot of the really useful refactoring in box these days so I no longer use it. I prefer to stick with Visual Studio but I know lots of folks who are happy with Rider. It's good for all of us when there is competition in paid for developer tools.