A bug in the Microsoft ReportViewer control

I found a bug in the Microsoft Report Viewer 2005 control. When used in LocalMode in an application that does not have a strongName signature, the reportViewer control saves temporary files to IsolatedStorage folder and does not ever delete the temporary files that it creates. So the result of this is that it takes up a lot of harddrive space, about 240k per page of the report. And when a report has 900 pages, this is a problemo. The problem is solved simply by making sure that your application has a strong name key (see the “signing” tab of project properties).

 

Nevertheless, this untidy habit of not cleaning up after itself caused me a lot of problems, several customer servers where this application is installed almost ran out of hard drive space because of this bug. Not good!

 

 

-Joseph

 

Comments

We are suffering from the exact same problem. The Isolated Storage folder is filling up with gigabytes of data. Other than the obvious fix of signing our assemblies and deleting the isolated storage folder everytime a new report is generated, is there a way to circumvent the problem? I've searched quite a bit on the web and this is the only reference I've seen of this problem. Any feedback would be greatly appreciated.
Anonymous said…
Your articles make whole sense of every topic.kill bed bugs
Unknown said…
This comment has been removed by the author.

Popular posts from this blog

RAM Disks do not speed up Visual Studio

How to Create and Run Tableau Bridge on Linux Containers

Outlook tip: Turn off Email Contact Pictures