I've recently run into an issue with with WPF 4 and the SSRS viewer control with a batch emailing application. See http://www.jenasysdesign.com.au/dnn/Blogs/tabid/71/EntryId/5/WPF-4-SQL-Server-Reporting-Services-processing-application-Memory-Leak.aspx for
details of some performance profiling issues I found with this technology stack.
I've got two issues.
Firstly, I implemented a background worker process to handling looping through the 2,800 reports. I found to run the SSRS report viewer to export the report results in a slow memory leak. See Red-gate Ants memory profiler 6 image in the link above. I'm not
sure what I need to do to remove weak references with this combination of technology. Any ideas?
Secondly, the following code runs on the background worker process, designed so the user can monitor the progress of the a large batch of report files getting generated. The catch here is involves using the SSRS viewer to export a reports results requires
the Dispatcher.Invoke method to ensure that ReportViewer.xaml screen gets a UI thread, but in the process it interferes with the background workers report progress methods, so the UI doesn't see the progress.
View Complete Post