Pre-built binaries for FSharp

[caxelrud]

Is it possible to distribute pre-built binaries for FSharp from Nuget.org (Microsoft.ML.Probabilistic.FSharp.dll)?

[tminka]

What do you want those binaries to contain?

[caxelrud]

I am referring to FSharpWrapper DLL.
Currently, I download the source code and compile it (Microsoft Visual Studio Community 2019 (2)).

Other related issues (I plan to open new issue items after repeating them to get details):
I had problems using the netstandard2.0 in the F# Interactive so I use the net461 found in the TestFSharp folder.
Currently, I can't use VSCode F# Interactive anymore because it is asking for DLLs. The same code can be used in Visual Studio 2019 F# Interactive with no issues.

[sir-deenicus]

Hmm curious, I just used Infer.net in VS Code (and VS 2019) with netstandard2.0 library and it worked with no problems.

[caxelrud]

I compiled the latest code from Github.
I tested, in VSCode, with the DLL from the folder: infer-main\test\TestFSharp\bin\Debug\netcoreapp3.1
It works. The problem that I am having with VSCode (and not with Visual Studio) is related to FSharp charting, more specific with
System.Windows.Forms.

[XiaoJiNu]

@sir-deenicus Could you please give the tutorial of runing infer.NET in vs code?

[caxelrud]

You can find examples that can be executed in VSCode at:
[https://github.com/caxelrud/Fsharp-and-infer.NET]
At this moment, for VSCode, comment all FSharp charting usage (I am looking for a solution on that).

[XiaoJiNu]

@sir-deenicus Thank you, but I use c#, I don't know whether it can be used for it.

[sir-deenicus]

@XiaoJiNu Do you know of .net-interactive? I think that's the easiest path for interactive development with C# and this library will give no problems running there.

@caxelrud Yeah, it makes sense that windows.forms is a cause. It might be the case that VS 2019 runs .net48 or so and vscode is on .netcore? With .net-interactive, plotly (xplot or plotly.net) are good.