Visual Studio Code for F# on .Net Framework

Hi there :wave:, have a good saturday! :grinning:

Is anyone using Visual Studio Code for a web F# project on .net framework :interrobang:

:white_check_mark: Just in case, how can I set up and build the solution (from the terminal? with an extension? thanks for the details)

:x: Fallback question: should the above be not doable, do you think I can easily move to .net core and propose the installation of .net core on the productive server without affecting the other apps running there on the .net framework (yet I’m not confident that the infrastructure team will accept such request :unamused:)

Can anyone at least point me to a doc explaining how to configure the integration of vs code with ms build for .net framework?
Thanks again

Edit

Maybe I’m confused but I’m afraid that what I’m trying to do is not possible.

The only thing I see is the possibility to do something like

dotnet build -f net461

But I can’t really compile a normal .Net framework project from Visual Studio MS Build in this way! Is this confirmed?

Edit 2

I’ve also tried the more promising

dotnet msbuild MySolution.sln

But I’m still getting an error:

C:\Program Files\dotnet\sdk\2.1.508\Microsoft.Common.CurrentVersion.targets(272
,5): error MSB4062: non è stato possibile caricare l'attività "Microsoft.Build.
asks.ResolveComReference" dall'assembly Microsoft.Build.Tasks.Core, Version=15.
.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a.  Verificare che la dich
arazione <UsingTask> sia corretta, che l'assembly e tutte le relative dipendenz
 siano disponibili e che l'attività contenga una classe pubblica che implementa
Microsoft.Build.Framework.ITask. [C:\dev\FSharp\microsoft\dotnet\MailForward\Ma
lForward.csproj]

This SO question (upvoted but almost unanswered) seems very related.

I’ve also tested a different kind of project and unfortunately I’m getting there a different error:

MSB4020: The value "" of the "Project" attribute in element <Import> is invalid.

So, in conclusion, I guess I should stick with the classical Visual Studio for all these projects