This is, unfortunately, a consequence of the annoying naming Microsoft does (I am allowed to complain about this because I worked on the .NET team -- nobody can

This is, unfortunately, a consequence of the annoying naming Microsoft does (I am allowed to complain about this because I worked on the .NET team -- nobody can name things we can't). You'll note that in the list of default templates: ASP.NET Core Empty web [C#],F# Web/Empty ASP.NET Core gR... grpc [C#] Web/gRPC ASP.NET Core We... webapi [C#],F# Web/WebAPI ASP.NET Core We... webapp,razor [C#] Web/MVC/Razor Pages ASP.NET Core We... mvc [C#],F# Web/MVC ASP.NET Core wi... angular [C#] Web/MVC/SPA ASP.NET Core wi... react [C#] Web/MVC/SPA "webapp" is actually a flavor of MVC with Razor Pages to define the UI, which is itself a flavor of UI that's different from the typical HTML/JS/react setup most people use. I think the cleanest way to do web development with .NET is to leave .NET-isms out of the UI (.NET UI is, ironically, its weakest link now) and keep it on the server.