Manage non package manager plugin version to multiple users

Hi everyone,

We are starting a new project in our company, and we need a system to manage the plugins we use, including their specific versions.

Our idea is to create a dedicated folder containing the required plugins with the correct versions. Some of these plugins are not available in the package manager, so we need a way to ensure everyone on the team uses the same versions.

Ideally, we want to change the directory where Grasshopper loads plugins so that it points to this folder. That way, when a user joins the project, they only need to update the plugin directory to access the correct versions. Similarly, if they switch to another project, they can revert to the original plugin directory to restore their previous setup.

Is there a way to achieve this? I’ve read that Grasshopper’s package directory may not be easily modifiable, but I’m not sure if that’s the case. Any advice would be appreciated!

Would it be an option fx to empty the Libraries folder and to add a path in the GrasshopperDeveloprSetting in order to set this new path with the plugins we are going to use?

Thanks!

Hi B.Balbastre,

This may help "Assembly resolver failed to load assembly" - #6 by Japhy

To do something that enabled you to deploy specific plugins per your different projects would be more involved (create a plugin of plugins?). I’ll see what we can do.

1 Like

Thanks for your answer, @Japhy. I understand that using the package manager makes sense in most situations. However, in large companies, we often work on multiple projects with different teams, and it would be beneficial to set up folders containing specific plugin versions. This is because different projects may require different versions of the same plugin.

For example, if I need to open a script I created five years ago, I want to ensure that the plugins remain unchanged rather than being automatically updated, just in case compatibility issues arise. This issue could be easily resolved if Grasshopper allowed us to change the plugin folder path.

Since that’s not currently possible, one potential solution is to keep the default Libraries folder empty and instead create project-specific environment folders, referenced through paths defined in the Grasshopper developer settings.

1 Like