To correct a common misconception:
VS Code DOES work with solution files.
It just has a weird UI for using them. You need to open the directory which contains the solution files. Then you’ll notice a little button on the left side of the bottom bar with a flame icon. Click on that, and a menu will pop up at the top of the screen allowing you to select from the available solution files. As soon as you select one, the Intellisense turns on!
And another common misconception:
VS Code IS a full IDE.
It supports full project files, integrates directly with the build system, and provides a debugger. It even provides version control integration (though only git for the moment). If you were building a straight .NET application, instead of a Unity program, you could do all of that without leaving VS Code. The UI feels more like lightweight text editors, like Sublime and Atom, but it still has all the features that make a full IDE.
And another one:
VS Code is currently a PREVIEW release.
It’s not feature complete. I can’t say with any certainty what features will be in the “full” release, but I know plug-in support will be among them. See the top suggestion in Microsoft’s VS Code uservoice page, with official developer response: http://visualstudio.uservoice.com/forums/293070-visual-studio-code
Thus far, VS Code is proving far faster and more stable than MonoDevelop. Yes, MonoDevelop provides Intellisense, but it’s slow and buggy.
Yes, MonoDevelop provides a debugger, and sometimes, if the stars align and perform the appropriate incantations to the Ancient Dark Gods of Code, it even manages to hit breakpoints without crashing. And if you’re one of the True Chosen Ones, you might even be able to inspect variables, though I’ve never seen this.
And VS Code’s text editor is almost as good as Sublime, which is not something I can say of any fully featured IDE I’ve tried before.