I would expect the unmanaged highs.dll included in the package to be copied to build output directory next to Highs.Native.dll.
I made a manual copy step in the build process to workaround this.
I'm using the 32-bit version because of other restrictions. NuGet package directory for the 32-bit native dll is runtimes/native/win-x32. This would typically be runtimes/native/win-x86. Does this atypical folder naming cause the dll to be missing from output?
I would expect the unmanaged highs.dll included in the package to be copied to build output directory next to Highs.Native.dll.
I made a manual copy step in the build process to workaround this.
I'm using the 32-bit version because of other restrictions. NuGet package directory for the 32-bit native dll is runtimes/native/win-x32. This would typically be runtimes/native/win-x86. Does this atypical folder naming cause the dll to be missing from output?