Update samples for correct architectural patterns#636
Merged
Conversation
guardrex
changed the title
halter73
approved these changes
Dec 17, 2025
Co-authored-by: Stephen Halter <halter73@gmail.com>
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
2 participants
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.
Addresses dotnet/AspNetCore.Docs#36427
Let's start by sorting out the sample apps.
How about we retain these and refactor everything around the true distinctions?
I understand now that what I was actually trying to do was have a sample without YARP/Aspire for those devs who don't want those implementations and that both are BFF approaches.
What I'm doing here thus far to demonstrate how this would work ...
BlazorWebAppEntraBfftoBlazorWebAppEntraBffYarpAspirein the 9.0 and 10.0 folders.BlazorWebAppEntratoBlazorWebAppEntraBffin the 9.0 and 10.0 folders.non-bff-patterntowithout-yarp-and-aspire.bff-patterntowith-yarp-and-aspire.... and BTW ... if we go this way ... it seems like the OIDC samples and article should also be updated. The so-called 'non-BFF' OIDC sample/article pivot is also BFF. Again, the difference (and what I was going for) is a non-YARP/non-Aspire version of your original samples.