I was simply referring to using the same C# files in multiple projects. In Visual Studio you can add an existing file to your project and link to the original location of the source file instead of copying it into the project directory.
Hey @stevebaer thanks for you help so far. We came with a solution that works for now. But still think it would be beneficial (for both us and McNeel) if this logic of loading in the most recent library would be ideal. Is this something that is on McNeel’s radar and if so, is it a fix we can expect soon?
Greets,
Rolf H
Sorry, but no this is not on our radar and not something you can expect a fix for soon. The situation is commonly referred to as “DLL hell” (DLL Hell - Wikipedia) and is not easy to fix from Rhino’s plugin loading logic. I would recommend either having your plugins all share some common code to eliminate the need for an extra DLL or place all of your rhps in the same directory and update your shared dll to the most recent one when new updates are made available.
Okay clear! Thank you for the explanation, we’ll have a look.