Comments on: NMath 7.0 & the .NET Standard Library

By: Trevor Misfeldt

Trevor Misfeldt — Fri, 18 Dec 2020 21:58:07 +0000

In reply to Trevor Misfeldt. We released NMath 7.2 today which uses Google OR Tools and is built on the .NET Standard Library.

By: Trevor Misfeldt

Trevor Misfeldt — Tue, 29 Sep 2020 20:49:08 +0000

In reply to Andreas Meeh. .NET Core can still use all of our optimizations if .NET Framework is available. So, not everywhere. Yes, this is an annoyance. We are looking at alternatives that will be better and .NET Standard compliant (fully-supported by .NET Core and .NET Framework).

By: Andreas Meeh

Andreas Meeh — Thu, 17 Sep 2020 10:27:42 +0000

Do you plan to replace the Microsoft Solver Foundation so that all optimizations can be used under .NET Core?

By: Trevor Misfeldt

Trevor Misfeldt — Fri, 31 Jan 2020 17:07:37 +0000

Please note that we have made an x86/x64 Windows package for those needing to target all Windows machines.

By: Trevor Misfeldt

Trevor Misfeldt — Tue, 30 Jul 2019 14:34:05 +0000

We have made a NuGet package with both Windows and Linux support (64-bit only) here: https://www.nuget.org/packages/CenterSpace.NMath.Standard.WindowsAndLinux.X64/

OSX could not be included because of size restrictions from NuGet.

By: Kapil M Bhudhia

Kapil M Bhudhia — Mon, 08 Jul 2019 08:36:58 +0000

@Trevor, can you let me know if the lib/NMath.dll library (from the nuget package) is the same for windows/linux/osx? I am trying to create a single nuget package and don’t understand what needs to be done with these different NMath.dll assemblies. I am blocked for now, your help in this regard would be greatly appreciated.

By: Kapil M Bhudhia

Kapil M Bhudhia — Sun, 07 Jul 2019 06:17:26 +0000

@Mark, @Trevor, did you find any smart solution to this. I have the exact same situation, which is creating a lot of hassle in creating a common nuget package (consuming nmath) for for linux and windows.

By: Trevor Misfeldt

Trevor Misfeldt — Tue, 02 Jul 2019 20:07:13 +0000

We definitely need separate ones because of the native functionality under the hood. This seems like a good suggestion. We will investigate it.

– Trevor

By: Mark Adamson

Mark Adamson — Tue, 02 Jul 2019 20:01:16 +0000

This is really great news and I look forward to implementing this in our code base.

Just one bit of feedback based on the nuget packages that we had made. The three separate packages that you have for different OSes means that we won’t be able to make shared packages that we can use locally on Windows and also on say Lambda.

Ideally you would just have one package, but if you need to have separate ones, then can you provide a common core package that they all depend on and that we can just add the OS specific ones to the top level tools. That’s how we previously managed x86 vs x64, we had a common package with nmath and nmath stats that all libraries referenced and then native packages that the top level packages referenced.

As it is, I expect we’ll end up making our own nuget packages again from the contents of these ones.