Skip to content
TaguaTaguaTagua

A Crystal Reports alternative for .NET 8, 9 and 10

Crystal Reports is one of the most common report writers in .NET applications, through SAP’s free Crystal Reports for Visual Studio. It runs on .NET Framework, and SAP has said it will stay there. An application that moves to .NET 8, 9 or 10, to ASP.NET Core or to Linux has to take its reports somewhere else. This page sets out where Crystal Reports for Visual Studio stands, the options, and how Crystal’s building blocks map onto Tagua.

Where Crystal Reports for Visual Studio stands

Section titled “Where Crystal Reports for Visual Studio stands”

As of September 2026:

  • It supports .NET Framework only. SAP’s FAQ says there are no plans to move to a framework later than 4.8: the product depends on C++ and COM.
  • Its runtime is a Windows installer. Since Support Pack 40, the 32-bit runtime is no longer supported.
  • It is still maintained: SAP lists the end of mainstream maintenance for Crystal Reports for Visual Studio at the end of 2029. Support Pack 40 added Visual Studio 2026.

So nothing forces you off it tomorrow. What it cannot do is follow the application to modern .NET, a Linux container or native AOT.

Your options

Section titled “Your options”
Option What it means
Stay on .NET Framework Keep the application, or a separate reporting service, on .NET Framework and Windows, with SAP’s runtime installed. It works until you want to move it.
Another report writer Rebuild the reports in a reporting product that runs on modern .NET. Some can import .rpt files through SAP’s runtime on a Windows machine; anything they do not convert is rebuilt by hand.
A code-first PDF library Rewrite each report as code. Full control, and the most work: layout, grouping and totals are all yours to write.
Tagua Rebuild each report as a Tagua template: readable YAML with bands, groups, expressions and totals, the concepts Crystal uses. It renders in any .NET 8 to 10 application, on Windows, Linux or macOS.

How Crystal reports map onto Tagua

Section titled “How Crystal reports map onto Tagua”

A Crystal report and a Tagua template are built from the same ideas, so a report is rebuilt section by section, not redesigned.

In Crystal Reports In Tagua
Report header and footer, page header and footer, details reportHeader, reportFooter, pageHeader, pageFooter, detail bands
Group headers and footers, “keep group together”, “new page before” groups, with header, footer, keepTogether and pageBreak
Database fields, parameter fields Dataset fields, and parameters with prompts and defaults
Formula fields Expressions: {Amount * 1.2:C} in text, and named variables
Summary fields (Sum, Count, Average…) per group or report Aggregates with a scope: Sum(Amount), Sum(Amount, 'report')
Running total fields, reset on a group or not Running aggregates: RunningSum(Amount), RunningSum(Amount, 'report'), RowNumber()
Special fields: page N of M, print date {PageNumber}, {TotalPages}, {Now():d}
Text, field, line and box objects, pictures text, line, rect and image elements, at their positions or in flowing layouts
Suppress (and conditional suppress) visible
Subreports, linked by fields subreport, with parameters from the current row
Cross-tabs matrix, with row and column groups and totals
Charts chart: column, bar, line, area, pie and doughnut

Running totals map onto running aggregates: RunningSum(Amount) restarts with each group, and RunningSum(Amount, 'report') runs on across the report; RowNumber() numbers rows. Formulas that keep state with WhilePrintingRecords and shared variables have no direct equivalent yet. In most reports they compute a running balance, which a running aggregate replaces, or a total a group header shows ahead of its rows, which Tagua’s aggregates give directly, since a group header can show its group’s total.

What you gain

Section titled “What you gain”
  • Modern .NET everywhere. Tagua runs on .NET 10, in ASP.NET Core, workers and Linux containers, and compiles with native AOT. There is no runtime to install.
  • Standards. One line makes the PDF accessible (PDF/UA), archival (PDF/A) or a Factur-X invoice. The same report also exports to Excel.
  • Templates you can read. A template is YAML, not a binary file: it reviews in a pull request, diffs cleanly, and previews as you edit.

Importing .rpt files

Section titled “Importing .rpt files”

Tagua converts SSRS and ReportViewer reports automatically (tagua import), and we are looking at doing the same for Crystal Reports. Crystal’s .rpt files are a closed binary format; the practical route reads them through SAP’s own runtime on a Windows machine, once, and converts the result to templates that then run anywhere.

Sources

Section titled “Sources”

Checked on 25 September 2026.