3 ms·
Looks like a sensible option for .Net Core development. VSCode and the command line tooling look to be pretty decent. I would really miss LINQPad though.
by jdking 10y ago
Looks like a sensible option for .Net Core development. VSCode and the command line tooling look to be pretty decent. I would really miss LINQPad though.
- rat87 10y agoI think Project Rider is probably going to be better then just VSCode.
- egeozcan 10y agoThe amount of time I've invested in LINQPad scripts means I'm going to keep dual-booting Windows in the foreseeable future.
- Rudism 10y agoThe csharp REPL is actually a fairly decent substitute for LinqPad. It can pull in 3rd party libraries, has autocomplete, and is all around quite nice to use. You don't get the automatically generated ORM against your database, but if you mostly use it to test code snippets or as a shell scripting substitute, you might be surprised by how little you miss it. When we migrated all of our .NET development to Linux where I work, I thought I'd have to at least keep a Windows VM around so I could continue using LinqPad, but the csharp REPL has pretty much sufficed for everything I do on a regular basis.