Now there is a fragmented headline! The reason for it is to hopefully guide people searching on this issue to this post, because it took me about a day of flexing my Bing-Fu before I finally came up with the correct search term that directed me to a solution.
A short explanation of what I was doing: I am fitting the new ReportViewer 10.0 control to a legacy application we have recently updated to .NET 4.0 / VS2010 in order to avoid having to expose the SSRS instance for clients to consume reports. Everything was going swimmingly, except for the fact that I could not get the loading div to display! Every single post on the matter seemed to state that it was the ‘default behaviour’ of the control to display this when you had the asyncRendering property set to True.
So after far too long searching for an answer, I ran an extra long report and fired up IE9 developer tools to see if I could locate the pesky div in question. Lo and behold it was there, but with display:none set. Are you serious? Why the hell was it doing that?
The search term that finally led me to the answer believe it or not was the clientId of the loading div. The solution can be found here but in short, if you have <xhtmlConformance mode=”Legacy” /> set, the spinner wont display. Either remove this, or set it to strict.
Why does this cause the issue? Who knows (probably a lack of testing on behalf of the SSRS team), I am just glad I found a solution.
Print | posted on Monday, 23 May 2011 12:18 PM