We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
This mode can handle traditional request/response and will also handle form posts with model binding where everything is server-rendered.
Looks very likely that this will quite quickly start replacing MVC and Razor Pages for new ASP.NET web apps since people will want to be in the nice Blazor component model.
Blazor SSR also seems like it will work great with other clientside options (any JS framework or approaches like htmx, Hotwired.dev etc) so we are not restricted to only go to Blazor Server or WASM for app interactivity.
Optimizely CMS and Commerce and Forms should support this mode and let partner developers work with .razor-files where the various CSHTML-views are used currently.