Piyush77

I'm trying to get some reports together using the new ReportViewer control, and having one slight problem that I can't figure out: The report display is blank in the web browser! I know it's getting results, because all the pages are there... they are just blank. I can also export the report to PDF or Excel and it comes out normally, it's just blank when viewing the html in the web browser.

Anyone have a clue what would cause that



Re: Visual Studio Report Controls ReportViewer - Renders Blank

Emo

I am having the exact same problem but it did not show up until I put the report viewer control in a content tag for a Master Page. Is there a known issue with the report viewer control and master pages in VS 2005



Re: Visual Studio Report Controls ReportViewer - Renders Blank

Lisa Nicholls

Hi guys,

I have experienced the same thing with master pages and the reportviewer control. I don't know if it is a known issue or not but I suspect it is. I read the item below (I have highlighted the important bit) on another forum. The advice that Wei Lu gave earlier in the thread was to remove the doctype spec from the master page.

I don't exactly know why s/he calls the doctype specification an "artifact" <shrug> and FWIW in my case my master page uses a different doctype. I use http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd, the person with the issue in this thread used transitional .

There is no way I am going to remove my doctype or change it -- all my CSS stuff requires the appropriate doctype to work in multiple browsers, since browsers look at this to decide how to handle various CSS subtleties. (I'm pretty annoyed about it...) But if you don't need yours, you could try it.

HTH,

>L<

(snip)-----------------------------------

(http://www.developmentnow.com/g/115_2006_8_0_0_814757/Problems-setting-webform-Report-Viewer-control-height-to-100.htm)

Hello Chris,

I think this is that the Report Viewer Control rendered the HTML code does not matc the XHTML artifact.

This issue is a known issue of the Report Viewer Control. I got this
workaround from the product team and they do not provide more detailed
information on this issue.

Anyway, I am glad to discuss more detail on this issue but since this is
relate the Report Viewer Control Code, I could not provide more detailed
information now. Thank you for your follow up.

Sincerely,
Wei Lu
Microsoft Online Community Support






Re: Visual Studio Report Controls ReportViewer - Renders Blank

Emo

Hi Lisa,

Thanks for the response. I got sidetracked on other issues but I will try some of the changes listed in the link and respond if it solves the issue.





Re: Visual Studio Report Controls ReportViewer - Renders Blank

Emo

Lisa,

I really apprciate the information but I have to agree with you in that there is no way I am removing the Doc Type from the Master Page. The negative impact of doing so greatly out ways any benifits. My solution for now is to simply not use Master Pages on this one page that has the report viewer control. I am also starting to rethink the use of Master Pages in general. This is a nice concept but I have found numerous "artifacts" that do not work the same on master pages as they do on normal pages. Tough call at the moment as I do like the consistent page structure the provide.

Joe





Re: Visual Studio Report Controls ReportViewer - Renders Blank

Lisa Nicholls

Hi Joe,

Were you able to confirm that master pages *were* the issue in your case

FWIW I know what you mean about master pages but I really like them and probably will not stop using them. I had practically invented a primitive version of them in ASP.NET version 1.0, that's how much I wanted to have them <g>. I was happy to switch over to the "official" version.

One thing that I have done is derived a MasterPage class (I mean, a class that inherits from System.Web.UI.MasterPage) and used that as a way of providing a sort of multiple inheritance scheme for page classes that don't have a common derivation themselves. IOW there is some common page functionality that I am able to call on without putting it directly in my page classes. I am sure I could have used a utility object for the same thing and am doing that for other stuff, but there were some advantages here.

What I'm thinking now is that maybe I could put some intelligence into my MasterPage class that could do something about deciding when to render the DocType. I don't know if it's possible -- but if you confirm that this is what is going on with you too, I think I will give it a shot.


What do you think

>L<