That does clarify things.
From time to time there are reports about systems not finding out that there is a new SR available (@brian), but I wouldn’t say that it is a wide-spread problem.
Two things come to mind as a way forward:
- The user will get the message that the plug-in was written for a newer version and will then hopefully manually check for newer versions. Or at least start asking questions about this.
- You can link to an earlier DLL - say from SR10 - when building your plug-in (of course not if there is something that you need in the newer version) so that it will install on all versions from SR10 onwards. Here’s @menno saying what he uses: Plugin Error: Rhino not up-to-date - #6 by menno