This is a migrated thread and some comments may be shown as answers.

Problem with ReportViewer Custom Skin

1 Answer 43 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Steve
Top achievements
Rank 1
Steve asked on 19 Nov 2012, 05:10 AM
Hi,

I hope there is an easy way to do this...  Basically, we have a perfectly running site which is built with many Telerik tools (love your products!)...  We just renew our annual subscription.

The Problem:  Our developed site, with extensive reporting and page richness thanks to Telerik, works super on IIS6 and IIS7.  All very nice.  We're sailing through a rebranding storm and have a new brand-related animated Gif for "Please Wait" which is now used throughout the site except for one place. That one last place to change is the Reportviewer for when it's processing data before the report displays.

So I came across a very nice thread on your site (http://www.telerik.com/community/code-library/reporting/general/applying-custom-skin-to-the-web-report-viewer.aspx) which explains: "You can do this by implementing a custom skin for the ReportViewer.".  So I did the following:

- I downloaded the Zip file in that thread and extacted the Skins folder and it's two sub-folders (Custom and Orange).

- In the "Custom" sub-folder, I replaced the Loading.Gif with my own Gif and then I copied that Skins folder to my project..

- I updated the properties in the page where the Reportviewer was happily living the past few years: SkinsPath="~/Skins" Skin="Custom"

- I hit the "Run" button and all was good in the world as it worked just as the thread said it would be.

So, then I copied the site to one of our servers (IIS7) and when you run a report at the site, it pauses a moment (new) when it's about to process the report and there's no font any more for the "Processing..." text and the animated gif is a box with a red x in it.  Then, the report processes and looks perfect, however, the toolbar is filled with those boxes with red X's in it and looks quite unhappy.

First, I thought it may be some IIS7 challenge the universe was throwing me, but I had the same results when I copied the site to a server running IIS6.

Then, I checked for the Skins folder on the servers and yes it was there with the right files in it.

Then, I removed the Reportviewer properties for SkinsPath="~/Skins" Skin="Custom" and I recompiled the site and reposted it (an automatic batch process) to both servers and both looked good again without any issue.

When the paramedics revived me, I found another thread on your site which talked about "the styles of the web report viewer's toolbar are all messed up" (http://www.telerik.com/support/kb/reporting/report-viewers/the-styles-of-the-web-report-viewer-s-toolbar-are-messed-up.aspx) and I meticulously went through every item in that solution path to no avail.

All that I need to do is to replace the animated Loading.Gif and I'm done but I've hit a wall here and hope you can bail me out like you have every time I hit walls in the past.

We're using: 

ASP.Net 4.0
VS 2010
Telerik Reports – Q3-2012
Telerik AJAX Controls – Q3-2012 

Please advise, thanks,
Steve    

1 Answer, 1 is accepted

Sort by
0
Steve
Top achievements
Rank 1
answered on 19 Nov 2012, 03:57 PM
I solved it...

When I originally had the Skins folder in the root of the site, I had this problem I reported, however, on a lark I thought to move the Skins folder to the folder where the Reportviewer page lives and viola!  That made it work.  I can duplicate this repeatedly for the "working" and "not working" scenarios.

Some thoughts for others that might come across this:

On the server (IIS6 or IIS7):

- When I place the Skins folder (containing my Reportviewer skin) in the root of my site, then it failed.  In this case, the Reportviewer properties are:  SkinsPath="~/Skins" Skin="Custom".

- When I place the Skins folder (containing my Reportviewer skin) in the same folder as the page which has the Reportviewer on it, then it works. In this case, the Reportviewer properties are: SkinsPath="Skins" Skin="Custom".

On my local machine with VS 2010:

- It works in all scenarios.

Steve
Tags
General Discussions
Asked by
Steve
Top achievements
Rank 1
Answers by
Steve
Top achievements
Rank 1
Share this question
or