VS Code basic usage

[enricosada]

It's an high level task, project affected can be ionide or a dependency like FsAutoComplete.

If possible work should be merged in the base repo (like https://github.com/fsharp/FsAutoComplete)

• .NET Core projects should not require mono installed ionide/ionide-vscode-fsharp#277 mono is not required for .net core only
• replace ProjectCracker with whatever omnisharp is using (msbuild as library, dunno) so is aligned with c# (more future proof, less hacks)
• Debugging inside VS Code #35 debuggin of .net core (netcoreapp1.0) projects
• works with app with project references ( like console + lib ), like a solution (or with .sln), support msbuild15 fsproj ootb (ref Support msbuild version 15 fsproj format ionide/FsAutoComplete#137 )
• fix .NET Core Sdk app/lib require a build before intellisense works ionide/ionide-vscode-fsharp#312 so will work without requiring a build before opening VS Code.

[cloudRoutine]

I've already been working on an alternative project reading mechanism for my ProtoWorkspace that is based on Omnisharp's approach.

• Project, Solution, & ProjectFileInfo Type Extensions
• SolutionFileInfo.fs
• ProjectFileInfo.fs

The issue I've run into with this is that F#'s lack of an extern alias means that some hoops will need to be jumped through in order to support reading both the old and new fsproj formats. Unless we want to build the migration functionality into this new project config reader in order to force everyone to update to the format.

If we pull this functionality out into a standalone tool I think we should merge it into FSharp.Compiler.Service replacing the projectcracker, not into FSAC. FSAC can use the dependency to get the functionality.

• msbuild myget feed

[cloudRoutine]

I just finished knocking out a basic project inspector that reads project options out of the new fsproj files

fsprojectile

The net46 build is the fully featured version that makes use of FCS, but since that isn't netcore compatible the netcore version uses a shim instead

[czifro]

May I make a suggestion? I think it would be nice, provided vscode offers the api, to order fs files in the left panel of vscode according to the compile order:

Compile order:

Displayed order:

I figured that if there is a move to do project inspection, then this would a helpful feature, especially since VS 20xx offers this (as well as Xamarin).

[enricosada]

@czifro custom treeview in vscode, to reflect Compile items is tracked in ionide/ionide-vscode-fsharp#248

[czifro]

@enricosada thank you for the correction! 😄

[enricosada]

Done, works in ionide 2.25.1.

atm require mono installed on non windows os (FSAC require it).