WPF/Silverlight report viewers troubleshooting

AUTHOR: Ivan Stefanov

DATE POSTED: July 09, 2014

With Q1 2014 of Telerik Reporting the style manager is no longer supported and instead implicit styling has to be used. There are few key things that you have to know which will help you when you add a Telerik Reporting report viewer to your applications:

1. By default Telerik Reporting gets installed with several xaml files and assemblies. Those files are needed for the report viewer and the controls it internally uses.

2. The files (xaml, assemblies) that get installed with Telerik Reporting are interchangeable with the ones that get installed with Telerik UI for WPF/Silverlight, given that they are the same version.

3. You are free to add those files(xaml, assemblies) either from Telerik Reporting or from Telerik UI for WPF/Silverlight.

4. If you add them from Telerik UI please make sure that you have also added the Telerik.ReportViewer.Wpf.dll and Telerik.ReportViewer.Wpf.xaml files. Please also make sure that they are the same version as the one required by Telerik Reporting or that you are using binding redirects if the version is newer.

5. If you add them from Telerik Reporting please have in mind that the controls provided in those assemblies are intended only to be used with the Telerik report viewer and any other usage would be violation of the terms of use agreement.

If a xaml exception is thrown when you are building your application or the behaviour is unexpected there are a few things that you might want to check in order to resolve the issue:

1. Check if you have properly added all the xaml files needed. A list can be found here (Silverligh) and here (WPF).

2. Check if you have added all the assemblies required. Again for a list check here (Silverligh) and here (WPF).

3. Check if the assemblies and/or xaml files are up to date (i.e. their version is equal or higher compared to the one required by Telerik Reporting).

4. Check if the version of the assemblies matches the version of the xaml files. In case they do not match exceptions may be thrown since some properties might be missing in an older version for example.

5. Check if you have binding redirects - they are needed if you are using a newer version of Telerik UI for WPF/Silverlight compared to the one distributed with Telerik Reporting. For more information on binding redirects please check here.

Possible exceptions:

• The type reference cannot find a public type named 'PickerToggleButton' - can happen when the version of the assemblies and the xaml files is different (they must match).

• The tag 'LogicalOperatorToCheckedConverter' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls.Data.DataFilter;assembly=Telerik.Windows.Controls.Data' - can happen when the version of the assemblies and the xaml files is different (they must match).