Telerik.Reporting.OpenXmlRendering 20.2.26.812

Telerik Reporting OpenXmlRendering

This package contains the rendering extensions that export a Progress® Telerik® Reporting report to the Open XML document formats — Excel (XLSX), Word (DOCX), and PowerPoint (PPTX). It is built against the Open XML SDK 2.7.2.

• Documentation
• Demos

What's in This Package

Supported Frameworks

• netstandard2.0 — .NET Standard 2.0 (.NET Core 3.1, .NET 5 and later)

Supported Platforms

Windows, Linux, and macOS, on-premises and in the cloud.

Requires

Install either this package or Telerik.Reporting.OpenXmlRendering3, not both. Choose this one when your project is pinned to the Open XML SDK 2.x.

Why Choose Telerik Reporting?

• Empower users with embedded reporting — let users create and customize reports in-app, reducing developer workload and turning data into decisions faster.
• Deploy anywhere with report viewer controls — embed interactive reports across .NET web and desktop apps, including ASP.NET Core, Blazor, Angular, React, HTML5/jQuery, WinForms, WPF, and WinUI.
• Build reports faster with intuitive report designers — create reports with drag-and-drop design tools for both code-first and low-code workflows, in the Standalone Report Designer, the Visual Studio-integrated report designer, or the Web Report Designer.
• Faster reports, clearer answers, powered by AI — streamline setup, speed up report design, and help developers, report creators, and end users get clearer answers from their data.
• Export to the formats your business runs on — PDF, Word, Excel, PowerPoint, CSV, images, and more.
• Connect to virtually any data — SQL and NoSQL databases, OLAP cubes, REST and GraphQL services, Entity Framework, JSON, CSV, and custom object data sources.

Trusted Enterprise-Grade Support

Get answers directly from the experts behind Telerik Reporting. Build confidently with a reporting solution backed by scalable architecture, comprehensive documentation, reliable performance, and expert support for .NET web, desktop, cloud, and on-premises deployments.

• Contact Support — technical support from the Telerik Reporting team.
• Community Forums — real-world questions, practical answers, and developer-to-developer knowledge to help you troubleshoot faster.
• Feedback Portal — share your feedback or request new features and components.
• Blog — expert-written articles and tutorials for developers.
• Discord Community — chat with other Telerik developers.
• Sample Source Code on GitHub — runnable examples for every supported platform.
• API Reference — complete type and member documentation.
• Release History — what changed in every release.

Get Started

1. Add the Telerik NuGet feed to your project and install this package:

   dotnet add package Telerik.Reporting.OpenXmlRendering
   

2. Design a report with the Standalone Report Designer, the Visual Studio Report Designer, the Web Report Designer, or in code. The desktop designers are not part of this package — they ship with the full product installer.

3. Display it with a report viewer or export it to one of the supported document formats.

For step-by-step walkthroughs, see First Steps in Designing Reports and First Steps in Integrating Reports.

License and Copyright

This is commercial software. By using it you agree to the Telerik End User License Agreement for Telerik Reporting. If you do not have a commercial license, your usage is governed by the trial license terms.

Telerik Reporting requires activation with a license key — this applies to both the trial and the commercial versions of the product. See Setting Up Your Telerik Reporting License Key for configuration and troubleshooting guidance.

Licenses can be obtained from the Telerik Reporting purchase page.

Copyright © 2021-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.

Packaged distributions of Progress® Telerik® Reporting obtained from NuGet are made available pursuant to the Progress Telerik Reporting EULA at https://www.telerik.com/purchase/license-agreements, unless you have entered into a separate MSA with the licensor.