Improve Blazor's static server-side rendering (SSR) capabilities to achieve feature parity with MVC and Razor Pages. This epic addresses key gaps that currently limit developers when building static SSR applications in Blazor, focusing on state management, helper methods, and output caching.

Objectives

This work aims to provide Blazor developers with the same powerful tools available in MVC and Razor Pages, enabling seamless migration and consistent development patterns across ASP.NET Core web frameworks.

Key Areas:

1. TempData Support - Enable temporary data storage between requests for static SSR scenarios, essential for post-redirect-get patterns and user notifications

2. Session State - Provide cascading parameter support for server-side session data, allowing components to access session state without manual plumbing

3. DisplayName Helpers - Add support for displaying model property names from Display attributes, similar to DisplayNameFor in MVC/Razor Pages, useful for scaffolding and form labels

4. Output Caching - Add a Cache component for Blazor that enables caching portions of rendered output, similar to the cache tag helper in MVC/Razor Pages

Success Criteria

• Developers can use TempData patterns in Blazor static SSR applications (e.g., for Identity UI and form submission feedback)
• Components can receive session data via [SupplyParameterFromSession] attribute
• Developers can generate display names from model metadata using helper utilities
• Developers can cache expensive component output using a <Cache> component with support for various render modes