3 ms·
Right now, there is a transition between net framework and net core in the MS .net world, which causes plenty of confusion to newcomers. Which is sad, because t
by AdeptusAquinas 8y ago
Right now, there is a transition between net framework and net core in the MS .net world, which causes plenty of confusion to newcomers. Which is sad, because the clean, .net core way is the simplest thing in the world:
1. Install the dotnet core sdk
2. From a command line in an empty folder, run `dotnet new console -lang F#`
3. To build or run use `dotnet build` or `dotnet run`
- turtlebits 8y agoWow, that actually worked. Wish those were in the official docs so I wouldn't have wasted an hour trying to debug... I followed the VSCode instructions and using "F# new project" apparently gave me a .fsproj with the wrong TargetFramework, and after changing that, then got a "Could not load file or assembly 'FSharp.Core" error.
- AdeptusAquinas 8y agoYeah, sorry. dotnet core to me has been an attempt by MS to not just get cross platform, but also to rewrite everything to get rid of the old kludges. Simple CLI, simple fsproj files, easy nuget, no differences on linux/osx/windows. But there is still a lot of outdated docs out there. dotnet core has just come too fast, imo (though I'm thankful). These MS docs are accurate: https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-command-line https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/g.... Though it does specify the use of sln, which isnt necessary for small projects.