Well I made some progress and understood few things better, but no
I never got
open MathNet.Numerics.FSharp
to work in FSI
What I learned more about dotnet was,
Install-Package in powershell is not the same Install-Package command that run inside visual studio and mentioned on the nuget site
The install-package command mentioned on the nuget site, is a command that runs inside visual studio
dotnet doesnt have (I think) a package manager that works like cpan or pip , nuget a project oriented tool, cpan or pip are system oriented tool
Inside fsi, opened with langversion preview
dotnet fsi --langversion:preview
#r "nuget: MathNet.Numerics.FSharp";;
open MathNet.Numerics.FSharp;;
Should have worked, but it doesnt , it does work for other libraries thought like Newtonsoft.Json
In the slack chatroom they explained to me that
#r "nuget: ...";;
In needed for some reason, and not redundant, but I forgot why
Anyway, the conclusion is, dotnet doesnt have a tool like cpan, and doest work like many other scripting languages that does have a cpan like tool
Its just easier to create a stub project to explore libraries and packages, dotnet is not for scripting
I dont think MS have any plans to make a real scripting language , and I still think that
#r "nuget: ...";;
Without a CPAN like tool, it is not enough … for scripting , I have not clue what is installed on my system and what isnt
Why does
#r "nuget: Newtonsoft.Json";;
open Newtonsoft.Json;;
work but
#r "nuget: MathNet.Numerics.FSharp";;
open MathNet.Numerics.FSharp;;
doesnt , I have no clue