Why SSRS Is Dead for .NET Core (And What to Do Instead)
SQL Server Reporting Services was the enterprise standard for .NET Framework applications. But Microsoft has not ported SSRS or ReportViewer to .NET Core/.NET 8+. Teams modernizing to the latest .NET face a hard choice: stay on legacy code or find an alternative built for the modern cloud-native world.
SSRS Is Stuck on .NET Framework
SQL Server Reporting Services (SSRS) has been the backbone of enterprise reporting for nearly two decades. It’s powerful, feature-rich, and deeply integrated with SQL Server. For .NET Framework applications, it was the natural choice.
Then came .NET Core. And then .NET 5, 6, 7, 8, 9, and 10. Microsoft built the modern .NET platform to be cloud-native, lightweight, and cross-platform. But SSRS remained frozen in time, locked to .NET Framework.
This creates a painful reality: if you’re modernizing a legacy .NET application to .NET 8+, you cannot bring SSRS with you. You have two options, both bad:
The SSRS Modernization Dilemma
Option 1: Keep SSRS. Maintain a separate .NET Framework server running your SSRS instance, even as the rest of your application runs on .NET 8. This means patching two different runtimes, managing dual infrastructure, and accepting technical debt that will haunt you for years.
Option 2: Abandon SSRS. Migrate to a modern reporting solution built for .NET Core. This requires work upfront, but you get a unified stack, cloud-native deployment, and no legacy infrastructure to maintain.
Most teams we work with choose Option 2 once they understand what’s at stake.
The ReportViewer Problem
Some teams think they can work around the SSRS limitation by using the ReportViewer control — embedding reports directly in their web or desktop applications without a separate Report Server. It sounds good in theory. In practice, it’s a dead end.
ReportViewer has not been meaningfully updated since 2017. The NuGet package exists, technically, but:
- No .NET Core support. ReportViewer is tied to .NET Framework and legacy ASP.NET. There is no official port to .NET Core or .NET 8.
- Blazor doesn’t exist. The web story for modern ASP.NET Core and Blazor is non-existent. You cannot embed ReportViewer in a Blazor application.
- Minimal maintenance. Microsoft has effectively abandoned the product. Security patches are rare, and new features are nonexistent.
- No cloud-native story. ReportViewer assumes a traditional on-premises deployment model. It doesn’t play well with containerization, Kubernetes, or serverless environments.
If you’re building greenfield applications on .NET 8, ReportViewer was never an option. If you’re migrating legacy code to .NET 8, ReportViewer needs to go.
What Teams Need Instead
Teams modernizing to .NET Core need a reporting solution that meets these criteria:
.NET Core / .NET 8 Native
Installs as a NuGet package. Runs in-process within your .NET application. No separate Report Server infrastructure.
Data Stays On-Premises
Queries your database directly from your application. Database credentials never leave your infrastructure.
Self-Service Reporting
End users can create and modify reports without writing SQL. No need for a dedicated reporting team.
No Separate Infrastructure
Everything runs in your .NET application. No SSRS server, no report server to patch and maintain.
Dotnet Report: The Modern Alternative
Dotnet Report is purpose-built for teams modernizing to .NET Core and .NET 8. It installs as a single NuGet package and brings enterprise-grade embedded reporting to your application in roughly 30 minutes.
What You Get
- Drag-and-drop report builder. Users select tables, columns, filters, and charts without SQL. They design reports visually.
- 12+ chart types. Line, bar, pie, area, scatter, bubble, gauge, funnel, waterfall, and more. All interactive.
- Multi-tenant by design. Built-in tenant isolation for SaaS applications. Each tenant has separate data, reports, and permissions.
- Scheduled reports. Cron-based scheduling with automatic email delivery (PDF, Excel, Word, CSV).
- Row-level security. Apply forced filters at the user or tenant level. Control exactly which data each user sees.
- API-first architecture. RESTful API for embedding reports, programmatic report generation, and custom integrations.
- AI-powered queries. Smart Query (beta) generates SQL and queries from natural language descriptions.
- Open-source frontend. The React-based report builder is open-source. White-label it, customize it, or build on it.
The 30-Minute Setup
dotnet add package dotnetreport
Configure two API endpoints. Connect your database (SQL Server, MySQL, PostgreSQL, Oracle, DB2). Deploy with your application. That’s it. No separate server, no infrastructure, no complex setup.
Flat Pricing That Makes Sense
Unlike SSRS, which charges per-user or per-core, Dotnet Report uses flat annual licensing. You pay once for unlimited users, unlimited reports, unlimited tenants. No surprise costs as you grow.
Why Flat Pricing Matters
SSRS licensing scales with your user base and server cores. As your application grows, your licensing costs balloon. With Dotnet Report, adding more users or tenants doesn’t increase your cost. This is especially important for SaaS platforms where per-seat licensing destroys your margins.
SSRS vs. Dotnet Report: Feature Comparison
Here’s how SSRS and Dotnet Report stack up across the capabilities that matter most for modern .NET applications:
| Capability | SSRS | Dotnet Report |
|---|---|---|
| .NET Core / .NET 8+ support | No | Full native |
| Setup complexity | Complex (server setup) | 30 minutes (NuGet) |
| Infrastructure required | Separate Report Server | Embedded in app |
| Self-service report builder | Yes | Drag-and-drop, 12+ charts |
| Dashboards | Yes | Live grid layout |
| Multi-tenancy | Add-on | Built-in |
| Row-level security | Yes | Forced filters |
| Scheduled reports | Yes | Cron + email |
| API-first design | Limited (SOAP) | Full REST API |
| AI query generation | No | Smart Query (Beta) |
| Cloud-native deployment | No | Docker, K8s ready |
| Pricing model | Per-user / per-core | Flat annual |
| Active development | Maintenance only | Continuous updates |
| Data residency | Can be on-prem | Always on-prem |
The core difference is simple: SSRS was designed for a different era. Dotnet Report is built for modern, cloud-native .NET applications.
How to Migrate from SSRS
Migrating from SSRS to Dotnet Report typically takes 2–4 weeks, not months. Here’s the process:
Step 1: Audit Your SSRS Implementation
Document every report, dashboard, and scheduled delivery your users rely on. Identify which ones are actively used (check usage logs) and which are dormant. You don’t need to migrate the ones nobody uses.
Also note your security model: user roles, row-level filters, and any multi-tenant isolation.
Step 2: Install Dotnet Report
Add the NuGet package to your .NET application. Configure two API endpoints. Connect your database — the same database SSRS was querying. Verify the connection works.
Step 3: Recreate Your Most-Used Reports
Start with your top 5–10 reports. Using the drag-and-drop builder, you can typically recreate a report in minutes. The most time-consuming part is matching any custom calculated fields or unusual formatting.
Don’t try to migrate everything at once. Get the critical reports working first.
Step 4: Configure Security and Multi-Tenancy
Dotnet Report’s security works through your existing .NET authentication. Set up role-based access controls and row-level security filters in the admin panel. For multi-tenant SaaS, configure tenant isolation — each tenant gets their own workspace with separate database connections, reports, and permissions.
Step 5: Run in Parallel, Then Cutover
Run SSRS and Dotnet Report side by side for a validation period. Have power users verify data accuracy and report functionality. Once you’re confident, remove SSRS and decommission the Report Server.
Pro Tip: Start Small
Teams that migrate fastest focus on their top 10 reports, validate with users, then expand. Teams that try to recreate every single report before going live tend to stall. Start small, validate, expand.
Common Questions
Do I need to keep my SSRS server running during migration?
No, but it’s often easier to run both in parallel for a validation period. Have your users check that the data in Dotnet Report matches what SSRS was showing. Once you’re confident, shut down SSRS.
Can I recreate my .RDL reports automatically?
No, .RDL files (SSRS report definitions) don’t port directly. But since Dotnet Report connects to the same database as SSRS, you’re not starting from scratch. You recreate the report logic using the drag-and-drop builder — typically much faster than you might expect.
What databases are supported?
SQL Server, MySQL, PostgreSQL, Oracle, and DB2. If you were running SSRS against one of these databases, it will work with Dotnet Report.
What about complex SSRS features like custom code in reports?
Dotnet Report covers the core feature set: filters, calculated fields, grouping, pivot tables, charts, scheduled delivery, row-level security, and multi-tenancy. If you’ve built complex custom logic into your SSRS reports, ask about it during the migration assessment. The answer is often “yes, we can do that,” usually in a cleaner way.
Will my end users need retraining?
The drag-and-drop builder is intuitive. Most users adapt in a session or two. The core concepts are the same — select fields, apply filters, choose a chart type — even if the interface looks different.
What about pricing compared to SSRS?
Dotnet Report uses flat annual licensing. For teams migrating from SSRS, the savings typically run 80–90%. You also eliminate the infrastructure costs of running a separate Report Server.
Can I keep some reports in SSRS and migrate others?
Yes, but it’s not recommended. Maintaining two reporting systems creates operational overhead and confuses your users. Our recommendation is to move everything to Dotnet Report as part of your .NET modernization.
Next Steps
If you’re stuck with SSRS on .NET Framework and need a modern path forward, here are three ways to get started:
Book a Migration Assessment
Free 30-minute call. We’ll review your SSRS implementation and outline what the migration looks like for your specific situation.
Start a Free Trial
Install the NuGet package, connect your database, and build your first report. No credit card, no commitment, no sales call required.
See the SSRS Migration Guide
View the detailed migration playbook with step-by-step instructions, timelines, and real customer stories.