Two part question about the Visual Studio templates for writing Grasshopper Component Libraries in C#.
First, is there a way to get them running in other IDE’s? Second, if I can’t do that, what would I be missing that I’d have to “hand roll”?
Long story short I am trying to get a linux box set up using the lightest weight development environment I can. Thanks in advance for your advice!
Personally as a Rider user (side note: Rider works on Linux AFAIK), I can’t remember any significant differences with set up, however modifing some parts (such as components’ icons) looks a little bit different.
Not sure if I understand correctly-would you be able to debug?
Thank you both for the input!
@w.radaczynski - that’s good to know. As @Baris says, are you able to debug?
And Baris - I’m also going to be using a purpose-built IDE for a less common language which fully supports .net… so I MIGHT be able to debug. But I am not taking it for granted. I think after everything else I might still need an IDE that has full debugging so VS might not be done with me yet whether I like it or not. (I don’t know if this language can use VS to debug…)
Mostly, I just didn’t know if there’s anything that is in the Templates for VS that I can’t get by say opening them in VS, saving the .cs files out with the appropriate headers etc and opening in another IDE…
In Rider I can debug. However side-note: once I started to unit test, debugging happens maybe once in a month 
Debugging is not just about hitting a breakpoint and step through the sources. There is a little bit more to it, and so to speak, you should use VS or Rider and nothing else for C#. I would even guess that VS is bloated to a great portion because of this. But sure you can use a lighter editor like VS Code and manually configure things until your brain explodes. For some languages this is indeed a better choice, but for C#, I would not miss VS. I have found many nasty problems thanks to its profiler, without much effort. No matter if regarding performance, memory leakage, concurrent issues or redundant calls. Turn on the profiler and you spot things you might never thought about.
And regarding unit tests, because it came up. I would not argue against automated testing things, but you can definitely waste a lot of time on this, having a high coverage and in the end still have a buggy app. Testing is good, but you can definitely overcomplicate the development process. A static analyser might already show you potential problems. In the end the IDE with best tooling wins in my opinion. BTW, occasionally I use DNSpy for debugging. It doesn’t need a PDB, but if you build one, you can always step through your sources anywhere.