I’m beginning to wonder if it makes sense to make our .NET SDK references available as nuget packages. I still haven’t thought the whole thing through so please bear with me.
The issue that I’m trying to solve is to make it easy for developers to get the appropriate DLLs in their plug-in projects for building plug-ins and GH components. This includes allowing developers to use older versions of DLLs than the current shipping Rhino for whatever reason they want an older version.
Another issue I’m trying to solve is to make the plug-in project more ‘portable’. Currently, the project references to DLLs like RhinoCommon or Grasshopper are possibly different on each machine since they are direct paths to the installed DLLs. This problem get compounded because the path to RhinoCommon on OS X is guaranteed to be different than the path on Windows. Currently this problem exists for RhinoCommon and Grasshoppper, but it is going to start happening for Eto and Rhino.UI as we move forward.
The RhinoCommon DLLs are going to be slightly different on Windows and Mac which I think nuget can solve too.
Any of you guys know enough about nuget to weigh in on this idea? Does this make our developers lives better or worse?