Installation Approaches for Telerik Reporting
Telerik Reporting provides options for installing the product by downloading the Control Panel, by using the MSI installer file, or with NuGet(adds assemblies to the project, no design time support).
Downloading the Control Panel
You can install Telerik Reporting by downloading the Control Panel. For the complete instructions, refer to the Optimizing Use of the Telerik Control Panel blog post.
Using the MSI File
You can install Telerik Reporting by using the
.msi file for automatic product installation. The file installs Telerik Reporting on your computer in a
Program Files/Progress folder, automatically creates the necessary virtual folders and projects, and provides all required files for developing with Telerik Reporting.
When you download the Telerik Reporting, the wizard for the MSI installation will by default install the product in the
C:\Program Files (x86)\Progress\Telerik Reporting R1 2023 folder for 32-bit machines, or in the
C:\Program Files\Progress\Telerik Reporting R1 2023 folder for 64-bit machines.
Using the MSI installer is the recommended way for installing Telerik Reporting. The MSI installer will automatically register the Telerik Reporting assemblies needed for Visual Studio Telerik Report Designer in the machine GAC, configure the Project and Item Templates in all Visual Studio instances, and create and populate the AdventureWorks sample database used by the sample projects.
During the MSI installation process, consider the following:
- Prior to R3 2017, the default installation paths were
C:\Program Files (x86)\Telerik\respectively.
- The latest package that is available for download has all updates/HOTFIXES applied already and you don't need to update it further.
- The MSI installation will not overwrite previous Telerik Reporting installations unless the current installation is of the same version. The installer will keep your existing installation. The new files will be placed in a separate folder and the new installation will not damage the common installer files.
- The Downloads page lists previously downloaded products. For any missing products or product versions, contact the Sales team through the support ticketing system by submitting a General Feedback thread.
- To access the latest Telerik Reporting internal builds, after you log into your Telerik account, navigate to Latest Internal Build under Downloads. For internal builds from earlier releases, select the respective Telerik Reporting version.
To install Telerik Reporting through the MSI automatic installer file:
- Log into your Telerik account. Click the Downloads tab to view the available trial and commercial products and select Telerik Reporting.
- From the next page, download the MSI installation and the documentation files and download the automatic installation MSI file. The source code is available for download only for commercial-license holders.
When the download completes, run
Telerik_Reporting_[suiteversion].msi. In the dialog which appears after you execute the MSI file, confirm that you have read and accepted the License Agreement.
In the dialog that opens, select the features you require.
- If Telerik Reporting does not locate a local SQL server instance on your machine or if your SQL browser service is stopped, the examples from the Examples dialog option will be installed but the configuration files for the application will not have valid connection strings. However, you can still access the working demos on the Telerik Reporting Demos page.
- To set up the examples and the used connection string, select Examples Setup. All local SQL Server 2005+ instances are supported.
- The examples use the MS SQL Server AdventureWorks database. Unless already available on your machine, the AdventureWorks database will also be deployed locally.
- Alternatively, you can install AdventureWorks by manually executing the SQL script from the installer. To use this option, navigate to [InstallDir]/Examples/Data/AdventureWorks OLTP. For the script to run correctly, uncomment the
SET @data_path = 'C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks OLTP\';statement and specify the correct path to the CSV data files which are in the same folder as the SQL script file.
(If Examples Setup was selected) In the Setup Wizard dialog, select your Database Server and the authentication for the connection. The Wizard detects all running instances and lists them in the input field.
To enable the Wizard to detect all running SQL Server instances, run the SQL Server Browser Service.
Using NuGet Packages
You can add Telerik Reporting to a project by using the Telerik Reporting NuGet packages. The NuGet packages are a single ZIP file with the
.nupkgfile contains the libraries for .NET Core projects, the Reporting Engine, and the implementation of the Reporting REST WebAPI-based service where you can use the packages with the standard .NET 4.6.1 framework.
- The Telerik Reporting NuGet packages do not include design-time support.
- The legacy https://nuget.telerik.com/nuget server is now deprecated. Make sure to switch to the new https://nuget.telerik.com/v3/index.json server, which is faster, lighter, and reduces the number of requests from your NuGet client. For more information on how to add a NuGet feed, refer to the official Microsoft documentation.
Adding the Telerik NuGet Feed
To install the Telerik Reporting NuGet packages, add the Telerik NuGet feed to Visual Studio and install the product. The following video demonstrates the steps for adding the Telerik NuGet feed to Visual Studio. If you prefer, however, you can follow the steps that are listed in writing after the video.
To configure the Telerik NuGet Feed in Visual Studio:
- Open Visual Studio and go to Tools > NuGet Package Manager > Package Manager Settings.
- Select Package Sources and then click the
+button to add a new package source.
- Enter a Name for the new package source, for example, Telerik NuGet.
- Add the
https://nuget.telerik.com/v3/index.jsonURL as a Source. Make sure the URL does not have a trailing slash. Click OK.
Handling Special Characters in Password
If your password contains a special character, those characters need to be escaped or it may fail authentication resulting in Error 401 login failure from the NuGet server. A common character that needs to be escaped is the ampersand
&, but it can be as unique as the section character
§. There are two ways to handle this.
- Change the password so that it only includes characters that do not need to be escaped
- HTML encode the password so the special characters are escaped (e.g.
We strongly discourage entering your password into an online encoder utility, use Powershell instead. Here's one example:
Add-Type -AssemblyName System.Web [System.Web.HttpUtility]::HtmlEncode('my§uper&P@§§word')
Installing Telerik Reporting
After you have successfully added the Telerik NuGet feed as a package source, you need to authenticate your local NuGet instance and install Telerik Reporting:
- Create a new Reporting project or open an existing one.
- Go to Tools > NuGet Package Manager > Manage NuGet Packages for Solution.... Select the Telerik NuGet Package source from the drop-down list on the left.
- Select the Browse tab to see the available packages. Enter your Telerik credentials in the Windows Authentication dialog.
- Select Telerik Reporting and click Install.