Closed danroth27 closed 11 months ago
@danroth27 why blazor server and not wasm?
@danroth27 why blazor server and not wasm?
For all the normal reasons that make Blazor Server a simpler model to get started with:
These are the same reasons why the Blazor onboarding tutorial on https://blazor.net is based on Blazor Server instead of Blazor WebAssembly.
Thanks for contacting us.
We're moving this issue to the .NET 8 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
If a user tried
dotnet new blazor
then they get an error, because the actual Blazor template names are blazorserver and blazorwasm.Describe the solution you'd like
Make
blazor
and alias for the Blazor Server template.Additional context
No response