several of our users report problems when updating to a new version of the plugin. As we have several DLLs that ship with the plugin it happens that Rhino loads a DLL from a previous version and the plugin does not work as intended.
I believe that the package manager should simply delete old version of the plugin when updating to a newer version.
Could you provide some more details about which DLLs are causing problems ?
It seems very likely that there could be another plugin that uses the same assembly as you but with an older version. In which case, the older one is most often going to be the one loaded in priority.
that is not the case. We only deploy library that we develop and have no third party dependencies. This is how our installation folder looks like (except the PDBs and exp).