3 ms·
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#, specifical
by bonesss 7y ago
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 7y agoFSI has never had package management. Are you referring to something else?
- bonesss 7y agoSorry 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/issues/3309 , https://github.com/dotnet/fsharp/pull/5850 https://github.com/dotnet/fsharp/pull/5850 , https://github.com/fsprojects/IfSharp/issues/206 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 ....