Sprite images not appearing with web.config skin entry

[Scott Buchanan]

I am using RadControls for ASP.NET AJAX Q1 2011.  I have an application where the Telerik controls have an unspecified skin (that is, there is no SkinID entry in the XML definitions).  I added the following to my web.config:

<add key="Telerik.Skin" value="Windows7" />

When I run the application, the CSS attributes (font, color, transperancy, etc.) are applied, but none of the background images that would come from the sprites are rendered.

I also tested

<add key="Telerik.RadGrid.Skin" value="Windows7" />
<add key="Telerik.Radmenu.Skin" value="Windows7" />

but no joy.

If I go to a control and specify

SkinID="Windows7"

then all is well - the background images are present.  I have reviewed (some of) the documentation, and it seems the web.config entry is a valid method to set the SkinID.  What am I missing?

Further - if a control has a SkinID attribute set, then the web.config entry overrides it (and works).  Please don't tell me I have to set a SkinID on all controls to use the web.config method.

Scott

 

 

 

 

 

[Dobromir]

Hi Scott,

I tried to reproduce the reported issue but to no avail. Could you please provide more detailed information on the specific scenario?

• Under which browser and its version the problem occurs?
• Do you experience this issue under IIS (and its version) or when the page is run through Cassini?
• Could you please provide a sample project reproducing the issue?

Could you try enable(if disabled) CDN or vice versa and see if the problem still occurs?

In addition, SkinID property is not related to the controls visual skin, but it refers to the declaration of the control in the Theme's skin file. The visual skin of the control is set through Skin property.
Kind regards,
Dobromir
the Telerik team

[Scott Buchanan]

I am developing with IE 9 and IIS 7.5.7600.16385 (Windows 7 64-bit SP1).

Before I dive into an example project, let me provide some additional details:

1. This application uses a custom skin (AmaPath), created with the visual style builder
2. The AmaPath.skin file (I assume created by a tool, but maybe another developer) contains entires like
   <telerik:RadMenu runat="server" EnableEmbeddedSkins="false" />
   for every control type used in the project.
3. No controls specify a SkinId, but many do have EnableEmbeddedSkins="false"
4. The CSS and image files are in the App_Themes\AmaPath folder
5. The web.config specifies both:

<add key="Telerik.Skin" value="AMAPAth" />
<pages theme="AmaPath">
    <controls>
    <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    <add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    <add tagPrefix="telerik" namespace="Telerik.ReportViewer.WebForms" assembly="Telerik.ReportViewer.WebForms" />
    <add tagPrefix="telerik" namespace="Telerik.Web.UI" assembly="Telerik.Web.UI" />
    </controls>
</pages>

 

This works great.  But we are making this available through another distributor, who demands a different look (skin).  We decided on Outlook.  I am struggling with how to preserve the functionality of the old skin and the new skin in the code base.

I assumed I could simply copy the Outlook folder from the \Program Files (x86)\Telerik\RadControls for ASP.NET AJAX Q1 2011\Skins folder to my project's App_Theme folder and update the web.config but no joy.  I also copied AmaPath.skin as Outlook.skin to the App_Theme\Outlook folder to attempt to use the local files instead of the embedded files (no difference).

I can go into the code and set the SkinID="Outlook" and EnableEmbeddedSkins="true" for some controls (and the web.config SkinId =Outlook) and all is well, but when I swithc the web.config back to the AmaPath skin then I have quite a mess.

Best,
Scott

[Georgi Tunev]

Hello Scott,

I am afraid that at this point I cannot tell what might be the problem - the logic that you used seems OK and I was not able to reproduce such problem locally. For convenience I attached a small sample where I use the Outlook skin as an external one via the ASP.NET Themes mechanism. I added a 3px border to the menu items just for testing purposes and to verify that the control is indeed using the custom skin.
Could you please check it and let me know if I missed anything? If I did, please modify the sample so it reproduces the problem and send it back in a support ticket so I can check it.


Best wishes,
Georgi Tunev
the Telerik team

[Scott Buchanan]

Thank you very much for the sample project.  I added my custom skin and was able to easily switch between the two skins using the

<pages theme="AMAPath"

in web.config.  I do not have it working in my application yet, but am confident I can now sort out the differences between your sample and my code and resolve it.

Thanks again,
Scott