{"id":119,"date":"2008-10-27T16:56:00","date_gmt":"2008-10-27T16:56:00","guid":{"rendered":"\/lisa\/post\/2008\/10\/27\/Walkthrough-Quick-branding-SQL-Server-Report-Manager-2005.aspx"},"modified":"2008-10-27T16:56:00","modified_gmt":"2008-10-27T16:56:00","slug":"walkthrough-quick-branding-sql-server-report-manager-2005","status":"publish","type":"post","link":"https:\/\/spacefold.com\/lisa\/2008\/10\/27\/walkthrough-quick-branding-sql-server-report-manager-2005\/","title":{"rendered":"Walkthrough: Quick-branding SQL Server Report Manager 2005"},"content":{"rendered":"

\nIt's been a month since my last post.  I have some excuse; C and I have moved again, we've found a place of our own in Marin (we've been looking since we joined EC<\/span>|<\/span>Wise<\/span><\/a> last fall). \n<\/p>\n

\nWe're nicely settled in, now, thank you for asking, and I can dig my computer out of the rubble.\n<\/p>\n

\nWhat took so long to accomplish a simple local move, you ask?  Why, the need to continue with real life (and real work) during this period.  \n<\/p>\n

\nAs part of what went on during my Blog Hiatus, I did a presentation required me to envision, and display, a fully-realized Reporting Solution that didn't yet exist. \n<\/p>\n

\nI bet this has never happened to you. OK now I will SET SARCASM OFF.  \n<\/p>\n

\nAs part of preparing it, I quickly and lightly "branded" a Reporting Services site  to serve as the host for some demo reports I whipped up.  In reality, we rarely use Report Manager as the vehicle for our reporting solutions, but this did the trick.\n<\/p>\n

\nAnd while I was doing this, I said to myself (with no sarcasm at all), "I bet this is something a lot of people don't know how to do".\n<\/p>\n

\nIf you do know how to do it, read no further. \n<\/p>\n

\nOr maybe you, like me, generally host RS content in your own interface, in which case this walkthrough probably won't help you except in the aforementioned "do this demo immediately" scenario.\n<\/p>\n

\nOr maybe all of your clients have happily moved to RS 2008 already. Perhaps this is no big deal at all in RS 2008?  You tell me — I haven't checked it out.  ("Come a day there won't be room for naughty men like us<\/a> to slip about at all…So here is us, on the raggedy edge.")\n<\/p>\n

\nBut if I've bet right, in your case — you don't know how to do this, and you might want or need to — keep reading, now you will.\n<\/p>\n

\nReady?  This screen shot shows you what we start with.\n<\/p>\n

\n\"Standard\n<\/div>\n

  <\/h4>\n

Step 1: Fix the site name.<\/h4>\n

\nThis is really easy.  You can do it through the ReportServer db, or you can do it through the Report Manager configuration pages.\n<\/p>\n

\n\"Fixing\n<\/p>\n

\n  \"Fixing\n<\/p>\n

Step 2: Fix the Report Manager styles.<\/h4>\n

\nThis one is not as easy, but almost.  Adjust ReportingServices.css in the appropriate location :\n<\/p>\n

\n \n<\/p>\n

\n\"Finding\n<\/div>\n

\nTake a copy of the "real" style sheet first, and keep it safe, obviously! Don't bother trying to point the Report Manager to a file with a different name. You'll still have to do something similar later (see next step) but don't waste your energy here.\n<\/p>\n

\nAt this point in your work, things are starting to look a bit better in Report Manager land…\n<\/p>\n

\n\"Report\n<\/div>\n

\n… but as you can probably see, especially when you demo reports,  you still have a ways to go.\n<\/p>\n

\n\"After\n<\/div>\n

  <\/h4>\n

Step 3:  Fix ReportServer<\/em> CSS styles.<\/h4>\n

\nWhen Report Manager hosts a report, it's really getting some of its presentation information for the embedded report from ReportServer.  We need to synch these things up.  We'll start with the ReportServer CSS stylesheet.\n<\/p>\n

\nThis step is similar to the last one, but in my experience you have to do two things, and both are needed.  If you don't do both, it looks like RS uses an internal version of its default HtmlViewer.css:\n<\/p>\n

    \n
  1. \n
    \n\tCreate your own CSS with a different name (say, MyHtmlViewer.css) based on the default HtmlViewer.css that ReportServer uses.<\/p>\n
    \n\t\"Adjusting\n\t<\/div>\n

    \n\t<\/div>\n<\/li>\n

  2. \n
    \n\tAdd a node referencing this new name to RSReportServer.config:
    \n\t <HTMLViewerStyleSheet>MyHtmlViewer<\/HTMLViewerStyleSheet> <\/strong>\n\t<\/div>\n<\/li>\n<\/ol>\n
    \n\"Pointing\n<\/div>\n

    \n \n<\/p>\n

    \nNow we're getting somewhere. But we're clearly not done.\n<\/p>\n

    \n \n<\/p>\n

    \n\"After\n<\/div>\n

      <\/h4>\n

    Step 4: Fix the Report Manager images.<\/h4>\n

    \nThe last screen shot shows you that ReportServer and Report Manager don't take care of everything by CSS.  You need to clone a couple of images, too.\n<\/p>\n

    \nIn this branding exercise I've deliberately changed the toolbar color significantly, so I'll need to change the toolbar edge GIFs provided by Report Manager to match.  I'll also change a few of the top-left icon images to match my vision for this site.\n<\/p>\n

    \nThis screen shows you the location of all the images, and also all four images that I chose to edit for this walkthrough.  There are two "toolbar edge" GIFs and two top-left icon JPG file:\n<\/p>\n