5 ms·
Thank you for these links. I will look at them! But I am wondering qualitatively, along the lines of whb07’s sibling answer: is the experience good? Is it as go
by dmitryminkovsky 7y ago
Thank you for these links. I will look at them! But I am wondering qualitatively, along the lines of whb07’s sibling answer: is the experience good? Is it as good as on Visual Studio?
- TomMarius 7y agoC# was usable in VS Code even 3 years ago
- dmitryminkovsky 7y agoHow is it these days? Is it “usable” or actually something you want to and enjoy using? Will I be left wanting Visual Studio? I mean I really enjoy IntelliJ, it makes programming Java like slicing butter. But I do want to try F#, people talk so highly of it.
- exyi 7y agoI work in VS Code (backed by Omnisharp language server) and I like it more than Visual Studio (it seems to be faster and has some good extensions). But it's not the same and does not contain all the features (and all extensions). Sometimes it annoys me that the debugger does not work as well. Other things that may annoy you is that you can't install R# and that VS Code basically ignores your solution file and uses directory structure.
- TomMarius 7y agoIntellisense was working 100%, but I stopped using it after that because I switched platforms. I don't believe it's worse today, VS Code as an editor is a joy to use (I use it with TypeScript).
- svick 7y ago> I really enjoy IntelliJ, it makes programming Java like slicing butter. In that case, I think you want an actual IDE and VS Code is not that. The options you have for .Net are Visual Studio and Rider (which is from the same company as IntelliJ and shares a lot of code with it).
- zamalek 7y agoIt (well, OmniSharp) is 95%. The 5% can be pretty frustrating (such as the lack of override autocomplete).
- ripley12 7y agoMy background is mostly .NET and web. I like VS Code a lot for JS/TS, but I hesitate to recommend it for C#. Using it about a year ago, I felt like I was missing a lot of the power of "real" Visual Studio and many language features were fairly buggy on my Mac.
- mattferderer 7y agoVS Code doesn't work for the older .NET Framework stuff (pre .NET Core). As for doing .NET Core stuff, it depends a lot on your setup of both Code & Visual Studio. Code has some nice features that you would need extensions or an upper tier VS version to get. Code can be faster at times as well. At the end of the day it is a different experience with a few pros & a few cons. It will greatly depend on the way you program.
- k_cieslak 7y ago> VS Code doesn't work for the older .NET Framework stuff (pre .NET Core). This is not true for F#.