Add a verified ASP.NET Core PDF download starter - #36
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a runnable ASP.NET Core PDF download using the published FullBleed.DotNet 0.1.2 package. The downloadable .NET 10 starter includes the Northstar invoice, bundled fonts/notices, a responsive download page, private PDF responses, and one native render per process with immediate backpressure.
The guide explains customization, account-scoped authorization, complete publish output, and the native API's cancellation limits. It links from the C# quickstart, examples, and navigation.
Validation: the actual ZIP is restored from a fresh NuGet cache, published, and run outside its source tree. Eleven checks pass on Windows and Linux, covering attachment headers and exact PDF bytes, text/total/preview, invalid requests, a concurrent burst, missing-glyph and missing-asset errors, and recovery. Both CI runs reproduce the same PDF and preview hashes. The workflow makes both checks deployment prerequisites.
The final PDF and 1440/320-pixel browser screenshots were visually inspected. Real Chrome keyboard activation downloaded the expected filename and byte-identical PDF, retained the page, and showed no horizontal overflow at 1440, 390, or 320 pixels. Strict local documentation and all 57 internal-page/link checks pass; full documentation CI is required before merge.
The sample contains fictional data and is not an authenticated billing application. No engine package or immutable release was changed.