[pjmlp]

Kind of. .NET Framework will be the XP of .NET until Microsoft provides an actual migration path to many of the APIs and frameworks that haven't made it into .NET Core.

Plus some of those APIs that made the cut into .NET Core, like the UI ones, are Windows only.

[bonesss]

There are also some critical tooling gaps that mean .Net Core is still broken for scenarios that worked a decade ago (FSI package management with F#, specifically).

[phillipcarter]

FSI has never had package management. Are you referring to something else?

[bonesss]

Sorry for the loose term. Not package management a la NuGet, but how packages and their references are handled (ie managed), so that they're not available and operative in FSI on .Net Core in VS.

Things that work when compiled, worked about a decade ago, but die on FSI preventing multiple data interaction & scripting scenarios. Ref: https://github.com/dotnet/fsharp/issues/3309 , https://github.com/dotnet/fsharp/pull/5850 , https://github.com/fsprojects/IfSharp/issues/206 , etc etc

Specifically, referencing a library that uses an FSharp.Data type provider, and calling that library in FSI in Visual Studio.

Updated to the latest and greatest, 5 y.o. code looks like this when we execute it:

> System.MissingMethodException: Method not found: 'System.String FSharp.Data.Http.RequestString(System.String ....