I'm using the Telerik.ReportViewer.Wpf.ReportViewer in my project.
We have had this installed for several years now and occasionally upgrade the dll files to keep up with the new releases. 13.0.19.222 is the release that I am upgrading to. Initially everything looked great. The report viewer is build, loaded and presented in a Rad Window. When I present it everything looks great. I return to my options dialog and click preview/print and the program throws an error suggesting that the PageScrollViewerSizeChanged property is null.
Something has changed in how the Report Viewer is behaving with this release.
Has anyone experienced this issue.
1 Answer, 1 is accepted
0
Hello Tom,
A more elaborate answer is already provided in the support ticket #1409046 on the same subject, but I will also explain it here for more visibility. When the report viewer's parent window is closed, the report viewer's resources and its model are being disposed in order to free up memory and optimize the visual tree. In the code you provided we noticed that the RadWindow is being closed and shown again instead of being instantiated, which will allow to initialize the report viewer properly. Our suggestion was to make sure the RadWindow that hosts the report viewer is instantiated every time before being shown. As a further optimization we can suggest to avoid closing the window each time and just show it if its instance is already created.
In order to provide better integration of ReportViewer with other host controls we will consider marking the viewer's disposal method as public and virtual so the developers would have more control on its execution.
I hope this explanation makes sense and provides the information needed to resolve the current issue.
Regards,
Ivan Hristov
Progress Telerik
A more elaborate answer is already provided in the support ticket #1409046 on the same subject, but I will also explain it here for more visibility. When the report viewer's parent window is closed, the report viewer's resources and its model are being disposed in order to free up memory and optimize the visual tree. In the code you provided we noticed that the RadWindow is being closed and shown again instead of being instantiated, which will allow to initialize the report viewer properly. Our suggestion was to make sure the RadWindow that hosts the report viewer is instantiated every time before being shown. As a further optimization we can suggest to avoid closing the window each time and just show it if its instance is already created.
In order to provide better integration of ReportViewer with other host controls we will consider marking the viewer's disposal method as public and virtual so the developers would have more control on its execution.
I hope this explanation makes sense and provides the information needed to resolve the current issue.
Regards,
Ivan Hristov
Progress Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items