-
Notifications
You must be signed in to change notification settings - Fork 10k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove stateful prerendering #12714
Remove stateful prerendering #12714
Conversation
src/Components/Server/ref/Microsoft.AspNetCore.Components.Server.netcoreapp3.0.cs
Show resolved
Hide resolved
aabe723
to
a3a482b
Compare
src/Components/Server/ref/Microsoft.AspNetCore.Components.Server.netcoreapp3.0.cs
Show resolved
Hide resolved
src/Mvc/test/WebSites/BasicWebSite/Controllers/RazorComponentsController.cs
Show resolved
Hide resolved
a3a482b
to
7b702df
Compare
src/Components/test/testassets/ComponentsApp.Server/ComponentsApp.Server.csproj
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues w/ the eng/ changes
0463028
to
41cfa1a
Compare
@SteveSandersonMS @javiercn - please take a look |
32f1338
to
5ad2679
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving because this looks great and I don't want to holding anything up, but please check #12714 (comment). My comment there might be wrong but if it's not it's definitely worth fixing.
e8f5e02
to
c1476cd
Compare
Fixes: #12245 Fixes: #12630 This change removes stateful pre-rendering from Server-Side Blazor. This means that when you render a component during the initial HTTP request, we we will no longer preserve the component instances and their parameters. While this feature was useful, it cause serious scalability concerns. This means that it will now be required to register "entry-point" components in startup similar to client-side Blazor.
c1476cd
to
2c64eae
Compare
Fixes: #12245
Fixes: #12630
This change removes stateful pre-rendering from Server-Side Blazor. This
means that when you render a component during the initial HTTP request,
we we will no longer preserve the component instances and their
parameters. While this feature was useful, it cause serious scalability
concerns.
This means that it will now be required to register "entry-point"
components in startup similar to client-side Blazor.