RhinoCommon NuGet file versions != installed file versions

Rhino Developer
1

Hi everyone,

I noticed that RhinoCommon’s latest NuGet package v. 7.15.22039.13001 contains the RhinoCommon.dll and the Rhino.UI dll with a previous file version: 7.15.22039.13000

In the latest Rhino, the file versions of both RhinoCommon.dll and Rhino.UI which got installed in my system are v. 7.15.22039.13001

There is a discrepancy between the NuGet package and Rhino’s latest update. Is there a particular reason for this? I feel that this should be fixed because if the NuGet package says the version is 7.15.22039.13001, I as a developer would expect that both RhinoCommon.dll and Rhino.UI file versions are 7.15.22039.13001 and not 7.15.22039.13000

image
image847×616 83.8 KB

I was aware of this problem, because in my project I am referencing RhinoWindows dll from my local machine, which depends on RhinoCommon.dll 7.15.22039.13001, causing me a build error.

I could simply reference these locally instead, but I really want to avoid this, as other projects in the solution are using NuGet.

@dale @stevebaer any input on this would be very helpful.

Thank you,

Nicholas

2

Hi @rawitscher-torres,

If you are referencing RhinoWindows.dll, then using NuGet doesn’t make sense. Modify your project and just reference the RhinoCommon assemblies directly, just like you are with RhinoWindows.dll.

– Dale

3

If you also reference RhinoWindows from NuGet then you wouldn’t see this error and your plug-in would load in 7.15.22039.13001 without any problems.

4

@will thanks for the pointer!

However, the question above has not been fully answered yet. Do you or @dale happen to know the discrepancies outlined above with the RhinoCommon NuGet package? To me it seems like a bug that can be easily fixed.

Thanks,

Nicholas

5

As of 7.16.22053.15001-rc and 8.0.22053.12305-wip the DLLs share the same version number as the nuget package.

1 Like