14 Aug 2012
06 May 2009
Link to this post
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?