Your missing out. C# is a really great and productive language. And with the advent of .Net Core it's cross platform and open source. What's not to love?
Tooling outside of Windows is really bad. I'm not completely discounting VS Code, they have been doing great work and might improve big time, but currently it's not an option.
MonoDevelop seems quite nice. I have only used it for F# but just the fact that its F# interactive has intellisense and syntax highlighting gives me good vibes.
I have tried both. VS Code lacks too many features still that are necessary for dealing with C# comfortably, while Rider is still immature (and isn't free).
What features are you missing? I've been using VS Code for 4 months now on a daily basis and can't say I'm missing anything outside of some Nuget package management tools, but I'm not sure if that's available to me and I just don't know how/where yet.
Were you using .Net Core, or .Net 4.X? The latter is all the C# I have to work with (mostly ASP.NET stuff), and that was pretty poorly supported last time I tried it; requiring me to roll a lot of files manually and so on (e.g. no "create new X page" style contextual options, no way to build project from editor and so on).
I'm writing an asp.net core app, my host os is macOS.
I initially setup my project with yeoman which created the footprint for me, but after that I've been manually creating files. You're right that it would be nice if it would create the file footprint for me but its only a couple of lines to add the namespace and class so it doesn't bother me too much, especially if you're used to text editors in general (I've used both a range of text editors with scripting languages and vs.net full in the past).
You can build via cmd+shift+b on mac, I assume swap the cmd for ctrl on PC, run is F5. These require properly configured launch.json and tasks.json files. cmd+shift+p brings up the command palette which lists everything you can do and their shortcuts.
The main things that make it viable for me (and differentiate it from a standard text editor) are intellisense, find references, rename symbol (method name, variable etc) and step through debugging. Without those id probably be leaning towards full VS on Windows or more likely for my particular situation Java being that I need to deploy initially to Ubuntu.
I do like the way Project Rider is going but I've found it a little buggy when debugging, so keeping half an eye on it as it progresses for now.
