Refer to my first post in this thread for my issues:
I think the 'bottom-line' with the control is simply that it was designed the wrong way around (apart from the bugs stated in the post referred to above). Providing a global skin manager yet have local skin definition override it, is just wrong, 'global' always comes before 'local'. This 'reverse' design makes it almost inevitable that issues such as i describe in the post linked to start appearing, had it been designed with the right state of mind (eg, global overrides local, as it should) the majority of such issues would never have seen the light of day. Things like the ' Skin="" ' bug, would not have been there.
This is not meant as an 'attack' on anyone at Telerik or Telerik itself of course, this is a common 'design mistake' made by untold amounts of developers. However, going in the correct direction with designing anything, often lessens the potential for 'stupid' mistakes to be made, makes certain bugs impossible from appearing, makes testing easier, etc. In this case SkinManager is a small thing, imagine an entire company nearly going bankrupt because of more than a decade of 'reverse designing' and their core business systems blowing up in their faces (an example of a project we're working on, fixing this entire company, from a to z).
It has not affected any of our current projects, we are still in the process of recreating our framework, and while i definitely want said functionality in the framework, it is not in there just yet (and won't be in the form of SkinManager at this point in time, due to the issues i stated). We may still move to another product suite as your product suite has resulted in sometimes scary amounts of work to get certain things done (and the same goes for other product suites of course, it is hard to tell what impacts harder on a per-suite basis, something i have yet to figure out based on the feedback from my developers).