Repository navigation
Keep homepage C# setup aligned with the executed quickstart - #162
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
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.
The homepage still installed FullBleed.DotNet 0.2.0 after the C# quickstart moved to 0.2.1, so copying the homepage commands missed the current pagination fixes. Update its install command and LINQ link to 0.2.1.
The existing verifier checked the shared C# source but missed the setup commands. It now checks both setup blocks, including the SDK target and package pin, before executing the guide. The guard reproduced the stale-homepage failure; after the fix, a fresh public NuGet install rendered the quickstart and the unchanged invoice/PDF preview successfully. Strict MkDocs and desktop/mobile Chrome checks passed.