I have a page with several rad controls on it, that locally looks fine on everyone's machine who uses this solution.

However once it is published to a web server, the controls no longer use the correct skin which is in the App_Themes folder.  I have checked for:

- Web.Config file has permissions to the folder (it does)
- Correct code is being published (it is)
- Same Telerik.Web.UI version on local as well as server (it is)
- Files are being properly published (they exist)
- Files are not corrupt and have the correct data (they do)

We are on Telerik.Web.UI version 2012.3.1308.40 

Attached are 2 sets of screenshots, one set marked Local, and the other Server...you can see what I am talking about.

Any ideas?

Hi David,

I am afraid that the provided information and the snapshots are not enough for determining the cause of the problem. Currently it looks to me like the ASP.NET Themes settings are overridden.

My suggestion is to ensure that the theme settings of the project are the same after deploying it. Please review this MSDN help article for more detailed information about setting a global (for the whole website) and a local (for a page) theme. You could also check if there are inline properties of the controls in the aspx file that are overriding the properties specified in the skin file in case the theme is included as a StyleSheetTheme.

If you continue experiencing the problem please get back to me with more detailed information about the project setup. Also, a sample project isolating the problematic would be very helpful for inspecting the issue locally and providing a proper solution.

Regards,
Ianko
Telerik

We managed to solve the problem using the web.config of a previous deployed project that worked correctly with our skins...doing a diff on the web.configs...they contained the same data / parameters however the <location path="Default.aspx"> tag was out of order from where it appeared in the new one vs the old one...i.e. it was the 5th item in the old version in the location tag declarations, but in the new one it was 6th...for some reason changing these fixed it.