Telerik.Reporting
This package contains the report definition APIs and the runtime report generation engine which are the core of the ProgressĀ® TelerikĀ® Reporting solution. The package can be used to programmatically export or print a report into multiple document formats like PDF, Word, Excel, PowerPoint. To author report definitions you need the Standalone Report Designer tool or the alternative Visual Studio integrated Report Designer. These tools come with the full product installer found at https://www.telerik.com/account/product-download?product=REPORTING Upgrading the project to a newer NuGet package version will upgrade the runtime libraries but for type report definitions (definitions created with the Visual Studio integrated Report Designer) you must run the Telerik Reporting Upgrade Wizard tool. The tool is part of the full product installer as well. IMPORTANT: This is commercial software. To use it, you must agree to the Telerik End User License Agreement for Telerik Reporting (https://www.telerik.com/purchase/license-agreement/reporting-dlw-s). If you do not have a commercial license, the usage of this product is governed by the trial license terms. Telerik Reporting requires activation using a license key ā this applies to both the trial and commercial versions of the product. Telerik Reporting licenses can be obtained through the Telerik Reporting page (https://www.telerik.com/purchase/individual/reporting). For more information on licensing, configuration, and troubleshooting, refer to the product documentation's License section (https://docs.telerik.com/reporting/licensing/setting-up-your-telerik-reporting-license-key).
Install
dotnet add package Telerik.Reporting --version 20.2.26.812
Install-Package Telerik.Reporting -Version 20.2.26.812
<PackageReference Include="Telerik.Reporting" Version="20.2.26.812" />
Frameworks
Dependencies
Adoption guide
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.
The published metadata declares 21 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.