Integration with WPF using Frame vs ReportViewer controls

I will forward this with stating that I am very new to WPF, but I'm a proficient SSRS developer, and have a good understanding of the ReportViewer control and capabilities of SSRS.

My question is regarding the pros and cons of using the WindowsFormHost > ReportViewer method vs using a WPF Frame to load the report URL directly.

It looks like using a Frame and handling the URL / Parameter logic behind the scenes would work just as well as the ReportViewer, but I would like other opinions on it, because I feel I am missing important details.

If I'm overriding the native toolbar with my own handling of Exporting and/or report parameters (regardless of method), what would be the difference between loading the HTML version of the report?

March 20th, 2015 4:48pm

Hi Aaron,

Thank you for your question. 

I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 

Thank you for your understanding and support.

Best regards,
Qiuyun Yu

Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2015 9:31am

Thank you. I wasn't sure if the WPF area would be a better reference point for this question, but the ReportViewer control is specific enough in use to point me to this area.
March 23rd, 2015 1:39pm

Hi Aaron,

Thanks for your question. I'm wondering which aspects are you comparing between these two methods? Performance, easy to use or functions?

Actually you are trying to compare between ReportViewer in Remote processing mode and WPF with Frame, right? And ReportViewer in WPF is still using as an Windows Forms controls. So you are trying to compare the rendering between GDI+ and HTML. Am I right?

Thanks,

Wynn

Free Windows Admin Tool Kit Click here and download it now
April 1st, 2015 3:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics