Hello Conrad Ehinger,
This issue is coming from the way the security and assembly signing in .Net framework works. We are having some solutions to this issue, but they are not yet implemented. For the time being, you can provide a readme file, explaining the people how to use the assembly version binding in the web.config - if they are using Sitefinity with version different than x.x.x.x, then they should include a record in the web.config file with the right version. This is similar to the way how we were upgrading the RadControls in the past, in case there's no Sitefinity release with the latest controls:
In the future, our solution would be most probably automatic assembly binding, or independent assembly that contains all the necessary API, and this assembly won't have it's version number changed with the releases.
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward!
We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>