Google.OrTools netstandard packages failing to install correctly in net472

[mwpowellhtx]

I have some .NET Framework targeted unit tests which I am updating from net45x to net472.

Others of my projects making the adjustment to netstandard2.0 work fine, but the Google.OrTools package is failing to add as a reference to my project following install.

Additionally, all of the run-times are being added as package references, when I think I should only be seeing the Windows package.

Consequently, any references to OrTools bits in the test assemblies are broken. Google.Protobuf package reference seems to be working okay, but I half expected that it would be fine.

For reference, kindly see my OrTools wrappers. Currently published versions are pre-netstandard2.0 updates. I've got those updates in the works.

[mwpowellhtx]

Part of me wonders if in fact it is a packaging, filtering issue. Another part of me wonders if for something like this it is even a tooling issue. I'm just concerned from an OrTools perspective what can be done to work over, under, through, around, etc.

[mwpowellhtx]

I can manually add the DLL reference, but I'm pretty sure with NuGet packaging involved, I do not want to be doing that, ever.

<Reference Include="Google.OrTools">
  <HintPath>..\packages\Google.OrTools.6.9.5841\ref\netstandard2.0\Google.OrTools.dll</HintPath>
</Reference>

[Mizux]

Did you try using PackageReference like I did in example/dotnet/*.csproj ?
Google.OrTools should contains the reference -> need to check the nuget package...

Currently Google.OrTools "umbrella" depends on the three runtimes.
If i remove the dependencies and only keep the runtime.json it seems that dotnet publish will retrieve the runtime (good) but dotnet build/run not (bad) IIRC.

I see a guy using a prebuild target or something similar to dynamically retrieve the runtime according to the RID when executing dotnet build. Need to retrieve how is done and if I can integrate it.

[mwpowellhtx]

@Mizux I'm not working with netcoreapp here. I am targeting net472 and working through the NuGet Package Manager.

[mwpowellhtx]

@Mizux I'm also not clear yet if/whether bits behind the scaffolding need to be or even can be better filtered depending on platform. The first thing for me is whether a NuGet Package Manager install happens cleanly end-to-end.

[mwpowellhtx]

Fingers crossed; replacing packages.config with net472 targeted <PackageReference ... /> so far so good.

[mwpowellhtx]

Hmm, I am receiving FileNotFoundException and BadImageFormatException exceptions.

I am building for AnyCPU, but I wonder should I build for x64?

System.IO.FileLoadException
Could not load file or assembly 'Google.OrTools, Version=6.9.5841.0, Culture=neutral, PublicKeyToken=600e580726a33e50' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
   at Kingdom.OrTools.ConstraintSolver.Samples.AspectBasedSudokuSolverTests.Verify_that_aspect_yields_solution()

[stuarthillary]

I have successfully been using the latest NuGet package within a .NET 4.7.2 project. The "trick" is to follow the advice by Scott Hanselmann here https://www.hanselman.com/blog/ReferencingNETStandardAssembliesFromBothNETCoreAndNETFramework.aspx

You need to add the node <RestoreProjectStyle>PackageReference</RestoreProjectStyle> within the first <PropertyGroup> of your csproj file.

[stuarthillary]

Also, you need to build for x64 as the NuGet package does not provide a 32-bit build.