aspnetcore/eng
Ryan Nowak 45f50905d5 Remove stateful prerendering
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.
2019-08-01 07:44:14 -07:00
..
common
docker
helix
scripts Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
targets Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
tools
AfterSolutionBuild.targets
Baseline.Designer.props
Baseline.xml
Build.props Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
CodeGen.proj
Dependencies.props
FlakyTests.AfterArcade.props
FlakyTests.BeforeArcade.props
GenAPI.exclusions.txt
LicenseHeader.txt
PatchConfig.props
ProjectReferences.props Remove stateful prerendering 2019-08-01 07:44:14 -07:00
PublishSymbols.proj
SharedFramework.External.props
SharedFramework.Local.props Remove stateful prerendering 2019-08-01 07:44:14 -07:00
Signing.props
Tools.props
Version.Details.xml [release/3.0] Update dependencies from 3 repositories (#12699) 2019-08-01 07:01:19 -07:00
Versions.props [release/3.0] Update dependencies from 3 repositories (#12699) 2019-08-01 07:01:19 -07:00
Workarounds.props
Workarounds.targets [release/3.0] Update dependencies from 3 repositories (#12699) 2019-08-01 07:01:19 -07:00
WorkaroundsImported.targets
configure-toolset.ps1
configure-toolset.sh