I can do this -

PS C:\foo> dotnet --version

1.0.0-rc4-004771 <- vs 2017 RC4

PS C:\foo> dotnet new mvc -lang F#

Pretty certain this is 4.1 and already out.

Articles have been around for a while https://medium.com/real-world-fsharp/using-f-with-net-core-a...

Fsharp 4.1 does not appear to be released yet. The download for windows is still 4.0. Last I looked ionide did not support .net core. I'm betting it will be released as part of the VS 2017 visualfsharp update. They just called for help testing RC3.

I'm looking forward to the release and the subsequent smoothing of the .net core fhsarp ecosystem.

Depends what you mean released. rtm not, but rc are out, and works.

Or use VS2017-rc, to use f# 4.1 with .NET framework

Or use .NET Core sdk and .net core https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-... the default templates use new f# 4.1

Ionide in vscode support .net core (both project.json and msbuild sdks), atm there is a temporary issues with rc4, but feel free to use a previous sdk (are really similar, no need to stay bleeding edge, and will be fixing sooner than later).

See wiki https://github.com/dotnet/netcorecli-fsc/wiki for more info about f# and .net core, or new sdk (all version, with how-to and workaround if needed)

A few things still need to be ironed up.

Expect full support around .NET Core 2.0 time.

https://github.com/Microsoft/visualfsharp/issues/2400

Awesome. IMHO to really "take off" fsharp is going to need a super smooth .net core story including .net core ionide support. It's not a sure thing, but I can't stress enough my belief in these two things:

* Seemless x-platform with dotnet core

* ionide working with dotnet core(and ideally on par with at least xamarin fsharp support)

First RTM release of VS 2017 due early March, but I think there will be many updates thereafter.