If I only messed with .NET Core I think it would be fine. I already use JetBrains Rider in place of VS.

The problem is that many systems still rely on .NET Framework which is a non start on Linux.

Also stuff like this:

https://github.com/dotnet/cli/issues/3093#issuecomment-44343...

Trust, is an issue.

and their response is even worst:

https://github.com/dotnet/cli/issues/10497#issuecomment-4494...

Sadly, I thought they would have fixed it and not ignore it.

Depends on if you're just writing pure libraries, or actually doing interesting things like UI or linking to 3rd party drivers.

I think the experience with mssql is better on linux now, but I imagine anything slightly outside the box db-wise may break you.

I know SQL for linux's docker image has been a breeze to work with, even in docker for windows. Also, SQL Operations Studio (electron based) is catching up to SSMS.

It's the lack of visual studio that is often the nonstarter.

Jetbrains’ Rider IDE is now so mature that I use it as a better Visual Studio even on Windows. It also runs on Mac and Linux. Great code manipulation, navigation and refactoring tools, and great support for adjacent technologies like build and test tools for both the .net code and web front-ends.

Jetbrains’ Rider is interesting.

Can you code on linux using Jetbrains to create .NET 3.5 apps for a Windows target? 3.5 is just an example because the matching VisualStudio works more or less in wine, while I haven't tested 4.0 and more recent.

.NET Core is the way to go if you want to be cross platform

https://dotnet.microsoft.com/download?initial-os=linux

I do not "want" to be cross platform. I just want to use popular frameworks with a large adoption.

(Working well inside wine qualifies as popular for me)

I'd think 3.5 had a greater user base than .net core.

You can get by with vscode for a lot, but not everything I think.

Is this purely about convenience tools in an IDE or are there some things actually locked into the Windows environment? Is .NET a lot like Xcode where it's not like you can just download the libraries + compiler + a text editor and have all you need? The latter is broadly true for every language I've really dove into so this feels like a foreign concept.

Edit: what I could stand to gain is that I work weekly in four or five languages. Already well tooled up in Ubuntu and vscode. Nothing frustrates me more than having to keep multiple IDEs consistent. Imagine driving two cars all day that have their controls in all different places.

Depends on what you're doing. Some technologies are only supported on Windows (like the official UI frameworks), but most things like webdev and gamedev libraries are supported on all platforms. Giving up Visual Studio can be a hard sell, as from my experience C# + Visual Studio (+ ReSharper) is one of the most productive programming environments you can have.

You can download the SDK from https://dotnet.microsoft.com/ and use it on any platform with your editor of choice, including JetBrains Rider, which is a cross-platform .NET IDE.

Depending on your UI needs, may want to look at Eto.Forms and MonoGame. :-) That said, I agree on productivity for C# + VS. I find I'm more productive with node + npm + vs code though.

.Net Core hasn't been too bad outside VS... I do wish they'd stuck to the JSON project format. I also wish dotnet had a task runner like npm in it.

The question here is - what do you gain? You're giving up arguably one of the best developer tools available for what? A slightly different desktop skin? Remapped shortcuts? Using slightly different command line commands?

VSCode really isn't even a same type of product than Visual Studio proper and it's nowhere near a replacement for VS heavy workflows.

I get by with it okay... generally only open full on VS when I HAVE to.

I don't doubt that. But that's not the point - I'm sure plenty of people get by with Paint or Paint.NET, but noone sane would call them a replacement for Photoshop and its workflows.

Same with VS vs. VSCode - I'm happy that it works great for you, but I'm not sure why you'd think they're comparable tools.

Reasonable. .NET Core is obviously fine, but even .NET Framework stuff is largely runnable with up to date Mono, as MS is slowly pushing lots of previously 'system' libraries into NuGet. WPF is the only notable big dealbreaker.

Web stuff is fine.