More in this section
Forums / General Discussions / Backwards compatibility of new Sitefinity versions

Backwards compatibility of new Sitefinity versions

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. Panos Klaoudatos
    Panos Klaoudatos avatar
    8 posts
    14 Aug 2012
    06 May 2009
    Link to this post
    Hi all,

    I recently updated a 3.6 project to 3.6 SP1 in which I had some custom skins of Menus, RadPanelBar, FormsDecorator,etc.

    When I updated the project, I had some problems with these skins and I had to 'tune' them in order to work in the new version. I also have some custom controls, based on SiteFinity controls, with added properties and functionality, which thankfully worked as well.

    I did read some posts about Sitefinity's team intention of making a skin builder. That is welcome.

    I have some questions though...
    Will the new versions of Sitefinity be backwards compatible?
    I have some 42 Sitefinity projects developed and I want to be sure that when I apply a patch or upgrade to a newer version, everything will run smoothly and I won't have to redesign skins or rewrite code.

    There was a face lift of RadControls skins 2008 to 2009Q1. For those who had develpoed custom skins, there was a lot of trouble of making the necessary changes. Apparently older custom skins were not compatible with the new Web.UI.dll. Is there a reason you decide to make such a change that affects previous code?

  2. Georgi
    Georgi avatar
    3583 posts
    28 Oct 2016
    08 May 2009
    Link to this post
    Hi Panos Klaoudatos,

    I can completely understand how you feel.
    The decision was taken by the RadControls teams in order to optimize the images, lower the bandwidth and the requests count. There are actually some extensive information on why we did this:
    And how you can migrate your controls in an easier way:
    Please take a look at this threads, and follow up if you have any further questions. I will forward them to our RadControls teams.
    Kind regards,
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
2 posts, 0 answered