Progress® Telerik® Reporting R2 2017

Upgrading Telerik Reporting Projects

There are two kinds of Telerik Reporting versions - major and minor. Major versions such as Q3 2013, Q1 2014, etc. can coexist simultaneously on the same machine. Minor versions are also known as Service Packs. There can be only a single major or minor version from the same Q installed on the machine, i.e. if you have version Q1 2014 already installed and a Service Pack is released (let's say Q1 2014 SP1), when you install it the installer will uninstall Q1 2014 for you.

Important note Important

Visual Studio Toolbox loads only the items from the greatest version of Telerik Reporting installed on the machine. You will be able to work with Telerik Reporting Visual Studio item and project templates of all installed Telerik Reporting versions.

Install a Newer Version

Install the new version of Telerik Reporting. If it is a major release it will be installed side-by-side. If it is a minor release it will replace the corresponding major release.

Old projects Auto Upgrade

Telerik Reporting offers a Telerik Upgrade Wizard which allows you to upgrade your project(s) to a newer version of Telerik Reporting. For more information on the wizard and which files are being upgraded please refer to the Telerik Upgrade Wizard topic.

Caution note Caution

Web Site projects are not supported by the Upgrade Wizard. In Web Sites assembly references are handled differently, and our recommendation is to upgrade manually or to turn the project into a Web Application that can be upgraded automatically - Web Application Projects versus Web Site Projects in Visual Studio.

Old projects Manual Upgrade

For all projects that need to use the new version of Telerik Reporting:

Web Site project:

  1. In Solution Explorer, click the "Show All Files" button.

  2. Delete all Telerik Reporting assemblies from the Bin folder.

  3. From the References tab on the Web Site’s Property Pages remove all references to Telerik Reporting assemblies. Remember the names of assemblies that you delete.

  4. Add all of the required references to the new versions of the Telerik Reporting assemblies. They should correspond to the ones that you deleted in the previous step.

  5. Open your web.config file and make sure that you change all version numbers to the new version number in the following instances:

    • <configSections> - this is where you can alter the rendering extensions attributes

    • <httpHandlers>/<handlers> - this is where the ASP.NET ReportViewer registers its handler

    • <assemblies> - the Reporting assemblies that are references in the Web Site

  6. Open your .aspx/.master pages and change the version of the ReportViewer in the Register directive.

  7. Open all report resource files (each .resx file appears under the respective report file) as XML. Locate all occurrences of a Telerik Reporting Assembly and update the version number to the new one. Unlike the version name (Q1 2014) a version number is a more technical identifier such as 8.0.14.225, for example.

  8. Restart Visual Studio.

  9. Rebuild all updated projects.

  10. In case you receive compilation errors and/or warnings, review the Release Notes – they contain an exhaustive list of obsolete and deleted properties, methods and events including information on what to be used instead, and why. Review the release notes of all Telerik Reporting versions starting from the version you upgraded from to the version you upgraded to, including the ones in between for information on how to update your project.

Feel free to contact us via the support ticketing system in case you still experience problems after the upgrade, and we will help you resolve any remaining issues. It will be faster and easier if you package your solution/project as a ZIP file and send it to Telerik, together with information on the errors/warnings you see.

Class Library project/Desktop application/Web application:

Important note Important

Manual upgrade is a must for Web Site projects, and for WPF and Silverlight projects which use the WPF and Silverlight ReportViewers without purchased separately Telerik UI for WPF and Telerik UI for Silverlight. In case you have Telerik Ui for WPF and Telerik UI for Silverlight installed on the machine, you can use the corresponding Upgrade Wizard to update automatically assembly references and XAML resources/

  1. In Solution Explorer, click the "Show All Files" button.

  2. Open the "References" node and locate the references to the old Telerik Reporting assemblies. In case you are installing a Service Pack you will notice that the Telerik Reporting assemblies have an yellow exclamation mark next to them, meaning that they cannot be located. That is because you have uninstalled the version that they belong to and is normal.

  3. Select the old assemblies that you located in Step 2 and hit delete to remove them. Remember the names of the assemblies that you delete.

  4. Right-click on the "References" node and select "Add Reference".

  5. Add all needed references to the new version of Telerik Reporting assemblies. They should correspond to the ones that you deleted earlier.

  6. Now they should appear in the "References" node without yellow exclamation marks, meaning that they are valid.

  7. Open your web.config/app.config file and make sure that you change all versions to the new one in the following instances:

    • <configSections> - this is where you can alter the rendering extensions attributes

    • <httpHandlers>/<handlers> - this is where the ASP.NET ReportViewer registers its handler

    • <assemblies> - the Reporting assemblies that are references in the Web Application

  8. Open your .aspx/.master pages (for web apps only) and change the version of the ASP.NET ReportViewer in the Register directive.

  9. Update the following HTML5 Report Viewer files in the project (for web apps only). Open your .cshtml/.vbhtml and layout views, pure HTMl pages or .aspx/.master pages  and change the version of the links pointing to these files:

    • telerikReportViewer-x.x.x.x(.min).css - the HTML5 Report Viewer’s stylesheets, where x.x.x.x is the HTML5 ReportViewer/Telerik Reporting version (e.g. 8.1.14.816).

    • telerikReportViewer-x.x.x.x(.min).js - the HTML5 Report Viewer’s JavaScript files, where x.x.x.x is the HTML5 ReportViewer/Telerik Reporting version (e.g. 8.1.14.816).

    • telerikReportViewerTemplate.html - the default HTML5 Report Viewer's template HTML page.

  10. Update the references to Telerik UI for WPF and the corresponding binding redirects, if any (for WPF apps only). For more details check WPF ReportViewer: Manual Setup..

    Update the XAML resources corresponding to the updated assemblies of Telerik UI for WPF.

  11. Update the references to Telerik UI for Silverlight (for Silverlight apps only). For more details check How to: Add report viewer to a Silverlight application.

    Update the XAML resources corresponding to the updated assemblies of Telerik UI for Silverlight.

  12. Open all report resource files (each .resx file appears under the respective report file) as XML. Locate all occurrences of a Telerik Reporting Assembly and update the version number  to the new one. Unlike the version name (Q1 2008) a version number is a more technical identifier such as 2.5.8.414, for example.

  13. Restart Visual Studio.

  14. Rebuild all updated projects.

  15. In case you receive compilation errors and/or warnings, review the Release Notes – they contain an exhaustive list of obsolete and deleted properties, methods and events including information on what to be used instead, and why. Review the release notes of all Telerik Reporting versions starting from the version you upgraded from to the version you upgraded to, including the ones in between for information on how to update your project.

Feel free to contact us via the support ticketing system in case you still experience problems after the upgrade, and we will help you resolve any remaining issues. It will be faster and easier if you package your solution/project as a ZIP file and send it to Telerik, together with information on the errors/warnings you see.