Blazor Visual Studio Templates Renamed as .NET Core 3.0 Finish Line Nears -- Visual Studio Magazine

Blazor Visual Studio Templates Renamed as .NET Core 3.0 Finish Line Nears

By David Ramel
08/13/2019

Even though the groundbreaking .NET Core 3.0 is nearing general availability and the dev team has switched gears to focus on stability and reliability, new tweaks and enhancements are still appearing in the latest preview 8.

For example, ASP.NET Core's Blazor project -- for Web development with WebAssembly and C# -- has simplified and renamed Visual Studio templates and a new replacement for the Blazor Class Library template, which is now Razor Class Library.

To follow a consistent naming style and simplify the number of templates, Microsoft said:

The "Blazor (server-side)" template is now called "Blazor Server App." Use blazorserver to create a Blazor Server app from the command-line.
The "Blazor" template is now called "Blazor WebAssembly App." Use blazorwasm to create a Blazor WebAssembly app from the command-line.
To create an ASP.NET Core hosted Blazor WebAssembly app, select the "ASP.NET Core hosted" option in Visual Studio, or pass the --hosted on the command-line

Meanwhile, the Razor Class Library template is now set up for Razor component development by default and the Blazor Class Library template has been removed in favor of new Razor Class Library projects that target .NET Standard, enabling them to be leveraged from both Blazor Server and Blazor WebAssembly apps.

Microsoft said it also cleaned up top-level Visual Studio templates so that some ASP.NET Core templates are no longer duplicated in dialogs, also noting that the Angular template has been updated to Angular 8.

The company's list of other changes in preview 8 includes:

Case-sensitive component binding
Improved reconnection logic for Blazor Server apps
NavLink component updated to handle additional attributes
Culture aware data binding
Automatic generation of backing fields for @ref
Razor Pages support for @attribute
New networking primitives for non-HTTP Servers
Unix domain socket support for the Kestrel Sockets transport
gRPC support for CallCredentials
ServiceReference tooling in Visual Studio
Diagnostics improvements for gRPC

More information is available in the release notes for .NET Core 3.0, which is expected to become generally available next month.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Using Local AI to Cut Copilot Usage-Based Billing Shock

After being gobsmacked by the new billing plan using almost all my monthly credits in one or two days, I tried pushing some Copilot-style coding work onto local models in VS Code. What I found was less "free AI" and more "pick your pain": cloud charges on one side, heavy local resource use and long waits on the other.
.NET 11 Preview 5 Focuses on Performance, Productivity and Safer Code

.NET 11 Preview 5 focuses on under-the-hood runtime performance gains, streamlined APIs and language features that reduce boilerplate, plus built‑in security checks and incremental ASP.NET Core and EF Core improvements aimed at everyday developer productivity.
VS Code 1.124 Focuses on Agent Autonomy and Parallel Sessions

Microsoft's June 2026 VS Code update turns on Autopilot by default and adds background sending for agent sessions.
Developing Agentic Systems in .NET: From Concept to Code

ZioNet founder Alon Fliess previews his Visual Studio Live! San Diego session on building true agentic systems in .NET -- covering the cognitive loop, MCP tool integration, multi-agent orchestration and enterprise hosting and governance with the Microsoft Agent Framework.