News for hackers. Stuff that matters.
Re:Visual Studio Code 1.6 by Pxtl on Monday October 10, 2016 @08:29PM (#12681005)
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?
Re:Visual Studio Code 1.6 by Arnavion on Monday October 10, 2016 @09:21PM (#12681246)
Both VS and VSCode use the Roslyn compiler to provide IDE functionality. https://github.com/dotnet/roslyn
Re:Visual Studio Code 1.6 by daeken on Monday October 10, 2016 @08:33PM (#12681037)
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.
Re:Visual Studio Code 1.6 by Pxtl on Monday October 10, 2016 @08:41PM (#12681076)
I thought project.json got mothballed? Did they take another kick at it and make it work?
Re:Visual Studio Code 1.6 by artimaeis on Monday October 10, 2016 @10:45PM (#12681540)
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.

Re:Visual Studio Code 1.6 by ctolkien on Tuesday October 11, 2016 @05:10AM (#12682709)
Project.json is getting pitched, but until the successor arrives, it's still the only way to do .Net Core dev.