Managing plug-in compatibility and .dll libraries

@stevebaer I am having Json dll problems again – I can get our GH plugins to work with new Newtonsoft dlls (version 12.0.2.0) if we manage our plugin ecosystem, but for some reason building an RHP that relies on Json functionality in the 12.0.0.0 release fails – Rhino 6 seems to be loading an older version and I can’t find where it is loading the dll or if it’s even possible to update it.

I’m targeting Rhino 6 SR8 in my plugins for compatibility with older installations but I’m running 6 SR13 and the problem persists.

Marc

I see – Rhino 6 ships with v10

Is there some way we can do away with this issue once and for all?? :slight_smile:

Can you just reference the Json.NET that ships with V6 and not ship that DLL? Same way you would reference RhinoCommon

1 Like

Here’s what I did – I am building the RHP for both Rhino 5 + 6, so I matched my JSON version to the one that 6 ships with (10.0.3) – this seems to be the best solution and so far works with 6 (haven’t tested 5 yet).

I’ve also downgraded my GHA dependency to the same version. So far so good.

Thanks,
Marc

1 Like

I made a note about how I implemented the new .NET API here:

I also implemented the CPython API outside of Rhino. Was also pretty straightforward.

1 Like

Does Rhino automatically on startup load the json.net dll that ships with it? It might encourage more use of it…