Static SSR in interactive app samples #471
Merged
Conversation
This file contains 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
|
One more thing tho ...... I have this in the wrong version folder. This is primarily for 8.0. For 9.0, there's a new attribute to take care of this. See ... https://learn.microsoft.com/en-us/aspnet/core/blazor/components/render-modes?view=aspnetcore-9.0#static-ssr-pages-in-a-globally-interactive-app I'll move these samples down to the 8.0 folder in a sec. |
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.
Addresses dotnet/AspNetCore.Docs#34630
Fixes #464
@silajim and @MarkusKirschnerLumivero ...
I'll take this live to the samples repo right after it builds. There's a sample app for each of the two scenarios. Next, I'm going to go over to the article section per dotnet/AspNetCore.Docs#34630 and make some minor improvements to the coverage.
Both samples seem to work fine from here. If you run into trouble with the article text, open an issue using the Open a documentation issue link/feedback form at the bottom of the article, which adds metadata for issue tracking and pings me on the main docs repo. It's the best place for us to work documentation issues.
If you have a NIT/question for the samples (not the article text), then this is a good repo for an issue.