# Service Release and SR candidate

**URL:** <https://discourse.mcneel.com/t/service-release-and-sr-candidate/36848>\
**Category:** Rhino Developer\
**Tags:** rhino5\
**Created:** [September 15, 2016, 10:20am UTC](https://discourse.mcneel.com/t/service-release-and-sr-candidate/36848 "2016-09-15T10:20:03Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![wim](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/wim/32/747482_2.png) [@wim](https://discourse.mcneel.com/u/wim)\
**Post date:** [September 15, 2016, 11:29am UTC](https://discourse.mcneel.com/t/service-release-and-sr-candidate/36848/4 "2016-09-15T11:29:25Z")

</div>

> [@MateuszZwierzycki](#):
>
> What I’m really talking about is that the computer with SR 12 […] says that it’s the most current version

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](https://discourse.mcneel.com/t/plugin-error-rhino-not-up-to-date/12205/6)

---

_[View the full topic](https://discourse.mcneel.com/t/service-release-and-sr-candidate/36848)._