We are using Telerik Radcontrols for ASP.NET AJAX in a custom CMS-type application that will be used to host hundreds/thousands of client sites going forward. The application uses 4 or 5 Telerik controls and for each client we usually start with a standard Telerik control skin and then make some (potentially a LOT of) changes to it for that client. So far, we have been making a copy of the original skin, giving it a new name and making any changes directly to that copy but I am concerned that as time goes on, Telerik will release changes to the controls that also require changes to the standard skins (like you did in the 2009-Q2 release with radpanelbar) that will require me to go make tweaks to all existing customized client telerik skins in order to deploy a new DLL. This will get very scary as the number of clients scale up so I am wondering if you would recommend that instead of me making changes directly to a base Telerik skin we should instead use a base skin and then create a separate "custom" CSS file that over-rides any needed changes from the base skin using inheritance? The thinking is that then if Telerik comes out with new releases that have new versions of skins or modified skins we just plug those in place of the old ones we are using and the custom "over-ride" CSS file for each client continues to do it's thing (in theory). Is there anything inherently better about the original approach or problems with the proposed new approach that I am not seeing?
Thanks in advance for any help you can offer.
Thanks in advance for any help you can offer.