| Invert |
Michael Hacker
03/25/2009 08:23
Debug-Informations from RSS & Components
Hi,
I find lot's of exceptions in my reports (calculate exceptions, DataNavigator...) in Visual Studio. To find it's causes today it's playing with trial and error (delete single pages, render report, when page with error is found, start to delete elements one by one , render and so on).
Is there any chance you implement a kind of debug-information which gives some more info in which part of my templates these errors are generated?
Nearby, after fixing my calculate exceptions my report was rendered 2-3 times faster.
Best Regards,
Michael
|
Anton Krotov
03/31/2009 01:56
Debug-Informations from RSS & Components
Hello,
You can handle the exceptions, which occur during the report rendering, using the call of ReportSlot.Prepare or ReportSlot.RenderDocument functions with parameter of the IRenderSite type. In order to do this create the object which is inherited from IRenderSite, redefine the needed methods in it and pass it as a parameter to the corresponding method.
Best regards,
Anton Krotov
Perpetuum Soft Support Team
|
P Nedved
09/08/2009 13:10
Debug-Informations from RSS & Components
Is there another (easier) way to get any sort of information besides "ExceptionDetailBase: Exception of type 'PerpetuumSoft.Reporting.Rendering.ScriptException' was thrown."?
I am suffering through the trial and error situations that the original poster noted.
I have tried to rig in an object that implements IRenderSite as a parameter to ReportSlot.RenderDocument, but I couldn't get it to work between the ReportManager.render call (I am working with the sample project in VB based on the your tutorial (http://perpetuumsoft.com/Product.aspx?lang=en&pid=102&tid=gettingstarted). To make it work seems like I'd need to change more than just what is stated. Please advise if I'm going about this all wrong.
thanks!
D.
|
Anton Krotov
09/10/2009 02:20
Debug-Informations from RSS & Components
Hello,
You can get additional information about rendering errors by the following way. There is RenderingError event in ReportSlot. If you subscribe to this event, you'll be able to get the appeared error from the parameter of RenderingErrorEventArgs type, passed to the handler of this event. You can do it using the following code: ((PerpetuumSoft.Reporting.Rendering.ScriptException)(e.Exception)).CompilerResults.Errors .
Best regards,
Anton Krotov
Perpetuum Soft Support Team
|