-
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
Rename the "ASP.NET Core Web App" template to "ASP.NET Core Razor Pages App" #50999
Comments
Perhaps better to keep with the naming scheme we used for MVC when we added Razor Pages, do we'd end up with:
Of course the challenge then is where does "Blazor App" fit in. Perhaps it's duplicated so that folks can just get to it either way. |
Yeah, this raises an interesting set of issues:
I don't love just taking over the ASP.NET Core Web App name with Blazor because then it's not clear that the template uses Blazor. And having two entries for the same template feels weird 😆 |
Options:
|
How about something like this?
Everyone knows what Razor, Blazor and MVC are, I think that's the easiest way to call templates. |
@Alerinos Thanks for the suggestions! We need to keep the "Core" in "ASP.NET Core" because we want to avoid confusion with ASP.NET for .NET Framework. We also don't need a separate Blazor SSR template, because the new Blazor Web App template already has an option for that: We also don't want to assume that everyone knows what these technologies are because we want to be approachable by new users who've potentially never used .NET before. Lastly, we typically also prefer WebAssembly to WASM in our naming because that's the name from the spec. I'm currently leaning towards this:
I know "Blazor Web App" doesn't make it clear that it's also an ASP.NET Core app, but I prefer the shorter name and we can clarify the ASP.NET Core relationship in the description. Thoughts? |
It makes sense to stick with
The new "Blazor Web App" is a merge of both The other option is for just a single
Lastly, there is one more type overlooked - ASP.NET Web App (Minimal API)... The last combined template will help reduce the total number of template types that we have to choose from, currently, 9+ template types with .Net 7.0 down to a single one. 11 template types if you include React & Angular. |
@gragra33 we've been hesitant to restructure the templates the way you suggest with options that ask the user to choose what stack they want, as it can also impact the CLI experience (CLI and VS share templates). That said, .NET 9 would be a reasonable time to revisit this and see if some template consolidation could result in a reasonable experience that satisfies most scenarios (new users, existing users, VS, CLI, etc.). |
The concern I have with this suggestion is that existing users will be more likely to just select "ASP.NET Core App (Razor Pages)" rather than gravitating towards our intended "new default" of Blazor. |
@DamianEdwards I hear what you are saying however there is [already] a large number of templates to choose from and feel that consolidation of some is overdue. If not consolidation, then suggest keeping the same naming convention to lessen the overload of everything new. You still have the question of how React and Angular fit into this... |
ASP.NET 2024 is maximum business can understand. |
I have a concern with changing the framework used in the "Web App" template breaks all documentation and tutorials that have been built on previous versions of ASP.NET Core. That content expects Razor Pages and would be somewhat forward-compatible without this change |
So many choices! Less is more, it should be really clear. I like what Damian had, but if you want could tweak it to add (Blazor) to the first so it is clear. And while it would break how docs expect it, it would still be more obvious. ASP.NET Core Web App (Blazor) They should be organized and numbered correct as well. Although if I am a new developer I still may be confused. With Xamarin.Forms and now .NET MAUI it is pretty simple with 1 template and just does it. With Xamarin.Forms you had different setup styles with or without shell, but just 1 template that asked you want you wanted. I don't think this is possible based on how the templates exist today. |
A community perspective: Largely outside this repository Microsoft is regarded as subpar at naming conventions and choices. You will find this idea ubiquitous across almost all forms of media when a name change occurs or is proposed. That being said the larger community rarely pays close enough attention to get involved - where they could have had input. Since Blazor is now just that "Blazor" but existing legacy web application templates are adorned with ASP.NET Core X - I would argue the convention already exists and should be followed. So, what @jamesmontemagno mentioned is clearly the logical preference and what I believe should be considered here overall. I would argue that "Model-View-Controller" could for conciseness be changed to "Razor MVC" though. With peace, Aqua. |
…#51157) # Rename "ASP.NET Core Web App" to "ASP.NET Core Web App (Razor Pages)" ![web-app-razor-pages](https://github.com/dotnet/aspnetcore/assets/114938397/3700cd64-cc7d-4817-87b3-17e38a83eb5e) ## Description Renamed "ASP.NET Core Web App" template to "ASP.NET Core Web App (Razor Pages)" Fixes #50999 ## Customer Impact The name for this template would be "ASP.NET Core Web App (Razor Pages)" in Visual Studio instead of "ASP.NET Core Web App". ## Regression? - [ ] Yes - [x] No [If yes, specify the version the behavior has regressed from] ## Risk - [ ] High - [ ] Medium - [x] Low [Justify the selection above] ## Verification - [x] Manual (required) - [ ] Automated ## Packaging changes reviewed? - [ ] Yes - [ ] No - [x] N/A ---- ## When servicing release/2.1 - [ ] Make necessary changes in eng/PatchConfig.props
In .NET 8 we are positioning Blazor as our recommended way to get started with building web UI with .NET and ASP.NET Core. Previously we would direct new users to use Razor Pages. To make it clear that the Razor Pages template was the preferred starting point, we game the Razor Pages template a very generic name: "ASP.NET Core Web App". Now that Razor Pages is no longer the preferred starting point, we should rename the template to be more specific: "ASP.NET Core Razor Pages App"
The text was updated successfully, but these errors were encountered: