Hi Mike,
In the project with the WPF ReportViewer you can use Telerik UI for WPF version common for the application, where you need to add binding redirects to specify that you are using version with greater number than the version used in the WPF ReportViewer - Redirecting Assembly Versions (msdn).
Visual Studio may not add the binding redirects automatically, which means you need to do it manually.
About using the WPF ReportViewer in an MVVM scenario, only dependencies properties of the viewer control (designed for WPF technology) can be bound to properties of the model. Thus your model can have a ReportSource property bound to the viewer's ReportSource.
If you need to change the data in the report, on changing data in the grid control you can update a report's DataSource in code and then the model's ReportSource in order to refresh the viewer.
Regards,
Stef
Telerik
In the project with the WPF ReportViewer you can use Telerik UI for WPF version common for the application, where you need to add binding redirects to specify that you are using version with greater number than the version used in the WPF ReportViewer - Redirecting Assembly Versions (msdn).
Visual Studio may not add the binding redirects automatically, which means you need to do it manually.
About using the WPF ReportViewer in an MVVM scenario, only dependencies properties of the viewer control (designed for WPF technology) can be bound to properties of the model. Thus your model can have a ReportSource property bound to the viewer's ReportSource.
If you need to change the data in the report, on changing data in the grid control you can update a report's DataSource in code and then the model's ReportSource in order to refresh the viewer.
Regards,
Stef
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