>>Please have in mind that only the default skins coming from Telerik
will be included as resources in the assembly.
>>All custom skins will
need to be added as external with EnableEmbeddedSkins=false
and register the skins manually
Yes, we know that, we have been using custom skins for a long time :)
The problem is that in Q1 2009 you changed the skins CSS structure completely, so even properly registered skins from 2008 look totally screwed up. We spent a lot of time perfecting every pixel on these skins and we do not want to go through the pain of doing it again. But we have to migrate to 2009 to get proper JQuery and Google Chrome support.
What should we do? Do you have consultants who specialize in your controls? We need to convert custom skins to Q1 2009 and we are willing to pay for it, but we do not want to spend any of our time on it...