Web Development with ASP.NET and Blazor

Complete guide and related articles on Web

Complete guide to web development with .NET: ASP.NET Core, Blazor, security and APIs to build solid, scalable web applications maintainable over time.

Practical guides on web development with .NET

2 articles found

When the web becomes a business asset

The web becomes a business asset when the application is not there just to exist, but to sell, automate processes, manage users, and support the business. In those cases frameworks, security, performance, and architecture make the difference between a published demo and a reliable platform.

Related web technologies

Sources and references

Martin Fowler - Software architecture

I use this source to ground structural decisions and explain why architecture is really about the economics of change.

Gregor Hohpe - Enterprise essays

This is useful when systems, integration, technical strategy, and organizational consequences must be discussed together.

Robert C. Martin - Clean architecture

I include it when the page needs to stress the link between code responsibility, clear boundaries, and long-term sustainability.

Frequently asked questions

ASP.NET Core MVC is ideal for APIs and server-side rendered web applications at scale. Razor Pages simplifies the model for independent pages with less boilerplate. Blazor is the choice when you want to write interactive UI in C# instead of JavaScript. The choice depends on the team (available JS skills), the type of interactivity required, and routing complexity.

Blazor Server keeps logic on the server and uses SignalR for communication: it is ideal when data is sensitive, the connection is reliable, and you want simple deployments. Blazor WebAssembly runs code in the browser: it is suited for offline applications, low UI latency, and CDN deployment. Blazor United in .NET 8+ allows mixing both modes in the same project.

ASP.NET Core offers ASP.NET Core Identity for cookie-based authentication with a database, and native support for JWT Bearer in REST APIs. For enterprise SSO scenarios, OpenID Connect is used via Microsoft.AspNetCore.Authentication.OpenIdConnect. In Azure the preferred token provider is Microsoft Entra ID (formerly Azure AD), natively integrated with MSAL and Microsoft.Identity.Web libraries.

Minimal API is preferable for microservices, simple APIs, and projects that prioritize startup speed and low overhead. Controllers with attributes remain the best choice for complex APIs with heavy logic, filters, complex binding, and large teams that benefit from explicit structure. It is not a matter of novelty, but of project complexity.