ASP.NET Core Report Viewer

The ASP.NET Core Report Viewer is a server-side reporting component that displays SSRS, RDL, RDLC, and Bold Reports® Server reports inside ASP.NET Core web applications. It renders reports directly in MVC controllers and Razor Pages without requiring a separate SSRS or Bold Reports® Server installation, though it can also connect to either when you need centralized report management.

This page introduces the Report Viewer, its core capabilities, and where to go next to add it to your ASP.NET Core application.

What is the ASP.NET Core Report Viewer?

The Report Viewer is a tag helper and API-driven reporting component built for the ASP.NET Core hosting model. It binds to data sources and report parameters, processes RDL and RDLC report definitions on the server, and streams the rendered output to the browser. It integrates with both the MVC pattern and Razor Pages, so you can host it in a controller action or directly on a Razor page depending on your application’s architecture.

The Report Viewer focuses on displaying and interacting with existing reports. Report authoring is handled by the separate Report Designer component, and reports can originate from local RDL/RDLC files, an SSRS instance, or Bold Reports® Server.

With the ASP.NET Core Report Viewer, you can

  • Display SSRS, RDL, and RDLC reports in an ASP.NET Core MVC or Razor Pages application.
  • Bind data sources and parameters, and render reports with full RDL reporting capabilities.
  • Export reports to PDF, Microsoft Excel, CSV, Microsoft Word, and HTML.
  • Print reports directly from the viewer without an intermediate download step.

Key features

Interactive report navigation

  • Drill-down and drill-through navigation between report levels.
  • Hyperlink navigation within report content.
  • Interactive column sorting.

Customizable UI and toolbar

  • Customize the toolbar, parameter panel, and other report items.
  • Match your application’s design and workflow.

Report processing events

  • Hook into events at each stage of report processing.
  • Customize data binding, parameter handling, and rendering behavior in code.

Multi-format export

  • Export to PDF, Microsoft Excel, CSV, Microsoft Word, and HTML.
  • Let users consume report data in the format that fits their workflow.

Common use cases

Embedding reports in business applications

  • Add reporting to internal dashboards and admin panels.
  • Works with both ASP.NET Core MVC and Razor Pages applications.

Connecting to SSRS or Bold Reports® Server

  • Display reports hosted on an existing SSRS instance or Bold Reports® Server.
  • Avoid duplicating report definitions locally.

Generating exportable reports for end users

  • Let end users view report output on screen.
  • Export it for offline use or distribution outside the application.

Building parameter-driven report views

  • Prompt users for report parameters at runtime.
  • Re-render the report based on their selections.

Who should use this guide?

This guide is intended for:

  • ASP.NET Core developers adding reporting to a new or existing application.
  • Developers migrating a reporting solution from ASP.NET MVC or ASP.NET Web Forms to ASP.NET Core.
  • Architects evaluating how RDL/RDLC or SSRS report display fits into an ASP.NET Core Razor Pages or MVC project.
  • Support and QA teams verifying report rendering, export, and parameter behavior.

Prerequisites

Before you begin:

  • An ASP.NET Core project (MVC or Razor Pages) targeting a supported .NET version.
  • The Bold Reports® ASP.NET Core NuGet packages installed in your project.
  • An RDL or RDLC report file, or access to an SSRS instance or Bold Reports® Server, to display.

No additional server software is required to view local RDL/RDLC reports; SSRS or Bold Reports® Server is only needed if you want to render reports hosted there.

Considerations and limitations

  • The Report Viewer displays and interacts with reports; use the Report Designer component to author or edit RDL/RDLC report definitions.
  • Report rendering performance depends on report complexity, data volume, and the hosting environment’s resources.
  • Some SSRS-specific features may behave differently depending on the SSRS version you connect to.
  • See the Limitations page for a complete list of unsupported scenarios.

FAQ

Does the ASP.NET Core Report Viewer require SSRS or Bold Reports® Server?

No. It can render local RDL and RDLC report files directly. SSRS or Bold Reports® Server is only needed if your reports are hosted on either platform.

Can I use the Report Viewer with Razor Pages instead of MVC?

Yes. The Report Viewer supports both the ASP.NET Core MVC pattern and Razor Pages, so you can host it in a controller action or directly on a Razor page.

Which report formats does the Report Viewer support?

It renders RDL and RDLC report definitions and can export the result to PDF, Microsoft Excel, CSV, Microsoft Word, and HTML.

Can I customize the toolbar and other UI elements?

Yes. The toolbar, parameter panel, and other Report Viewer elements are customizable, and report-processing events let you control rendering behavior in code.

Getting help

If you run into an issue while integrating the Report Viewer, check the FAQ and How to sections for solutions to common scenarios. If you still need assistance, reach the Bold Reports® support team by submitting a support ticket with details of your issue.