F# support

Maybe it’s not the right place to ask, but i have seen comment in .net blog to give feedback here.

Maybe it’s already in roadmap, or discussed, i tried to search this repo/visualfsharp/internet, but my google foo failed so i opened this issue.

I really liked the idea in comments about having a single .netproj ( like old xproj/project.json ) with a simple compilerName to drive c# vs vb vs f# vs newdotnetlang, was extensible and simple. For example i can now open a xproj f# and works (not intellisense) but everything else (publish, etc) is ok. Also .netproj extension name is really awesome. So a shared project file plus some extensibility works, so where to extend?

I see in #40 the cleanup of csproj continue, that’s great, moving default in language targerts, plus and some comments from @davkean about naked .proj

and final line in csprj is about

  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />

That said, with current cps requirement, it’s possible to make the .Managed read an msbuild property and use the required classes ( .CSharp, .VisualBasic ) instead of subclass? And file extension with old proj? So all .csproj / .vbproj are really the same project. I know cps capabilities help to share, but how that intesect with having different proj? 😕 With old system was really easy (and bad for f# and other proj ) to create a special item/feature for a specific project flavor. i understand cps help a lot about that with capabilities.

If not possible, this repo is the right place to subclass for adding the required host-agnostic and vs layer .FSharp project? inheriting from .Managed? With .net cli ( now .net core sdk 😄 ) having all the glue code in a single repo helped to have it aligned, was easier with the code changing a lot, until the good extensibility was in place with .net sdk tools ( dotnet-compile-{compilerName} ) and the language specialization is extracted.

If it’s not there the place np, but to untangle things, it’s possibile to have a pointer what are the missing pieces? f# lack a roslyn workspace?

I’d like to help implement what’s missing, to fully support F#

[dsyme]

🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉

[davkean]

We’ve added support for F# in 15.5.