More in this section
Forums / Deployment / Problem with versions of RadControls

Problem with versions of RadControls

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Miguel Reig
    Miguel Reig avatar
    7 posts
    15 Feb 2006
    29 Mar 2011
    Link to this post
    We have a problem with the versions we are using RadControls for development:

    Sitefinity uses 2010.3.1109.40 version, but instead the system uses the latest version 2011.1.315.40.

    If you try to upgrade the project to the latest version, Sitefinity stops working...

    If you use the 2010.3.1109.40, Visual Studio tries to use the other and produces errors at design time.

    How we can make it work?

    Thank you!
  2. Steve
    Steve avatar
    3037 posts
    03 Dec 2008
    31 Mar 2011
    Link to this post
    A default install should have the Telerik.Web.UI referenced in the bin folder, not your install folder, and while it may seem tempting to run the upgrade wizard I don't think that's a supported scenario :)

    Grab the install version 1109.40 form the _EmptyProject install folder, drop it into your bin.  Make sure the project references that, and all other projects also reference that DLL.  Don't do that Add Reference thing and find Telerik.Web.UI from the .NET tab...

    Or you can get ballsy and use the latest Telerik.Web.UI at your own risk with Assembly binding.
            <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
                    <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />
                    <bindingRedirect oldVersion="" newVersion="2011.1.315.40" />
                    <assemblyIdentity name="Telerik.OpenAccess" publicKeyToken="7CE17EEAF1D59342" />
                    <bindingRedirect oldVersion="" newVersion="2011.1.316.10" />
    So this is what I'll route any request from an old version over to the "newVersion" you have specified (as long as it exists).  Our main site has a ton of custom server controls all compiled against different versions of the Web.UI, but as long as that binding is there, they all just auto-magically co-exist.
2 posts, 0 answered