Re:Visual Studio Code 1.6
by daeken on Monday October 10, 2016 @05:42PM
(#12679981)
I've recently switched to VS Code full time for C# and Python development and I couldn't be happier. While I miss some of the more intelligent intellisense from full VS, I love that I can do all of my dev on OS X. Its integration with .NET Core makes my life easy; really can't complain at all.
[ Parent
| on HN ]
Re:Visual Studio Code 1.6
by JoelBennett on Monday October 10, 2016 @06:21PM
(#12680199)
I was curious to know how it worked for Python. I might have to give it a serious go...
I wish it did a bit more in the way of completing methods on objects (it sometimes will, but only in super clear-cut situations), but outside of that it's solid. Completely replaced Sublime for me, outside of the subl command line.
Really, for c#? I assumed that the type-inferencing in and extension methods would make proper IDE support of C# on a "light" platform like vscode impossible. How do you manage your vcproj file?
Both VS and VSCode use the Roslyn compiler to provide IDE functionality. https://github.com/dotnet/roslyn
I figured the same! But it handles type inference, extension methods, using static, etc like a champ. Even does completion for project.json. I don't use vcproj since I just use dotnet core.
I thought project.json got mothballed? Did they take another kick at it and make it work?
Don't recall ever hearing it got mothballed during development - though I do believe they've bent over and are going to support csproj files with .NET Core in the future as well.
Here's the relevant page on project.json: https://docs.microsoft.com/en-us/dotnet/articles/core/tools/...
Edit: I need to be better about deep reading through links. https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-t... looks like project.json will be mothballed. Kind of.
Project.json is getting pitched, but until the successor arrives, it's still the only way to do .Net Core dev.
Re:Visual Studio Code 1.6
by matthewking on Tuesday October 11, 2016 @04:03AM
(#12682502)
Seconded, I've been writing c# with asp.net core solely on OSX for a few weeks now, I've not run into a single thing that I miss from full Visual Studio yet, living the dream!