.Net Core / .Net Standard 2.0

Question

.Net Core / .Net Standard 2.0

kraptor23 opened this issue 7 years ago · 8 comments

Any plans to support .Net Core / Standard? I would love to use this library in my core application (MathNet Numerics in use already).

Answer 1 · 2018-01-17T20:22:10.000Z

Yes, my plan is to support .Net Standard 2.0 for all Math.NET projects. But so far I've postponed any investments until Numerics v4 is released, so we can reuse its tooling which has by then proven to work well.

Answer 2 · 2018-01-18T07:25:57.000Z

Thanks for the update - I look forward to v4!

Answer 3 · 2018-06-05T13:57:50.000Z

Just checking in on this - MathNet Numerics is awesome - any progress on migrating the other projects - especially Symbolics?

Answer 4 · 2018-08-20T08:49:16.000Z

I keep my fingers crossed for .NET Standard version :)

Answer 5 · 2018-10-22T21:15:05.000Z

Math.NET Symbolics v0.19 and newer support .Net Standard 2.0.

Answer 6 · 2018-10-29T02:15:45.000Z

@cdrnet, paket.bootstrapper.exe has been renamed, but restore.cmd and restore.sh have not yet changed. Please update them.

[edit]
I found a typo in Symbolics.Tests.fsproj:

<RootNamespace>MathNet.Smbolics.Tests</RootNamespace>

Answer 7 · 2018-10-29T08:52:08.000Z

One more, no tests are shown in the Test Explorer again.

Build.cmd is working fine. In VS 2017, building itself is OK, but there are errors in the Tests and Package Manager output pane.

Tests Output Pane:

[2018-10-29 PM 5:15:57 Informational] ------ Discover test started ------
[2018-10-29 PM 5:15:58 Error] System.InvalidOperationException: The operation failed as details for project Symbolics could not be loaded.
   at NuGet.PackageManagement.VisualStudio.NetCorePackageReferenceProject.GetPackageSpecsAsync(DependencyGraphCacheContext context)
   at NuGet.VisualStudio.VsPackageInstallerServices.<GetPackagesPathResolverAsync>d__8.MoveNext()
...

Package Manager Output Pane:

Error occurred while restoring NuGet packages: The operation failed as details for project Symbolics could not be loaded.

I installed the latest dotnet cli from here.

Answer 8 · 2018-10-29T19:21:15.000Z

Thanks for the hints. I've fixed the first two, but I don't think we can get the VS Test Explorer to work easily again (due to limitations of the VS adapter).