dotnetreport.backend
6.3.5
dotnet add package dotnetreport.backend --version 6.3.5
NuGet\Install-Package dotnetreport.backend -Version 6.3.5
<PackageReference Include="dotnetreport.backend" Version="6.3.5" />
<PackageVersion Include="dotnetreport.backend" Version="6.3.5" />
<PackageReference Include="dotnetreport.backend" />
paket add dotnetreport.backend --version 6.3.5
#r "nuget: dotnetreport.backend, 6.3.5"
#:package dotnetreport.backend@6.3.5
#addin nuget:?package=dotnetreport.backend&version=6.3.5
#tool nuget:?package=dotnetreport.backend&version=6.3.5
dotnetreport.backend
The Dotnet Report server code on its own: the API, report exports and scheduled reports.
| Package | What's in it | Install it in |
|---|---|---|
dotnetreport |
Everything | A single web project |
dotnetreport.frontend |
JavaScript, CSS, images, Razor views, the two page controllers, gulpfile and npm package list | The web project that hosts your views |
dotnetreport.backend |
API controller, report model, scheduled job and their NuGet libraries | Your .NET API project |
Install dotnetreport.frontend and dotnetreport.backend at the same version. The backend package also works on its own behind the Angular or React front end.
What's included
Controllers/DotNetReportApiController.cs: the API the front end calls, and the proxy to the Dotnet Report serviceModels/DotNetReportModel.cs: report models, the database helper, and Excel, Word and PDF exportJobs/DotNetReportJob.cs: scheduled report emails
Installing the package also adds the NuGet libraries these files need, including OpenXml, EPPlus, Quartz and PuppeteerSharp.
Copy the files into your project
Commit your project to source control first, so you can merge any customizations back in after an upgrade.
Add
GeneratePathProperty="true"to the package reference:<ItemGroup> <PackageReference Include="dotnetreport.backend" Version="x.x.x" GeneratePathProperty="true" /> </ItemGroup>Add this target to the project file and build once:
<PropertyGroup> <ContentFilesPath>$(Pkgdotnetreport_backend)\contentFiles\any\any\</ContentFilesPath> </PropertyGroup> <Target Name="CopyDotNetReportBackend" BeforeTargets="PreBuildEvent"> <Copy SourceFiles="$(ContentFilesPath)Controllers/DotNetReportApiController.cs" DestinationFiles="$(ProjectDir)Controllers/DotNetReportApiController.cs" /> <Copy SourceFiles="$(ContentFilesPath)Models/DotNetReportModel.cs" DestinationFiles="$(ProjectDir)Models/DotNetReportModel.cs" /> <Copy SourceFiles="$(ContentFilesPath)Jobs/DotNetReportJob.cs" DestinationFiles="$(ProjectDir)Jobs/DotNetReportJob.cs" /> </Target>Remove the
CopyDotNetReportBackendtarget after the build. Otherwise every build overwrites your changes.Add your Dotnet Report keys to
appsettings.json, and addJobScheduler.Start();toProgram.csif you use scheduled reports.
See the knowledge base for setup and upgrade guides.
Learn more about Target Frameworks and .NET Standard.
-
- DocumentFormat.OpenXml (>= 3.3.0)
- EPPlus (>= 4.5.3.3)
- HtmlAgilityPack (>= 1.12.4)
- HtmlSanitizer (>= 9.0.892)
- Microsoft.Data.SqlClient (>= 6.1.4)
- Newtonsoft.Json (>= 13.0.3)
- PdfSharp (>= 6.1.1)
- PuppeteerSharp (>= 20.2.4)
- Quartz (>= 3.15.1)
- System.Drawing.Common (>= 4.7.3)
- System.Text.RegularExpressions (>= 4.3.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 6.3.5 | 36 | 10/6/2026 |
6.3.5 (first release of the backend package)
- Excel and Word exports and scheduled emails keep outer group layouts, heading styles and table formatting.
- Word exports of outer-group reports end with a report total, with a subtotal per group when that option is on.
- Clicking the header of a Month/Year column sorts it by date instead of by month name.
- Choose Column Label is used in Excel, PDF, Word and CSV exports.
- Scheduled Excel exports use each report's saved subtotal settings, matching the browser export.