🔥 Building a Clean Architecture with Blazor


Today's Sponsor:

HackerPulse — The Ultimate Dev Profile

Don’t send 69 links to share your work - just share one!

Bring together your GitHub, Stack Overflow, and LinkedIn profiles into a single HackerPulse dev profile. Perfect for job applications and networking, HackerPulse gives a complete picture of your skills and projects, all in one place.


Hey Reader,

Today, I'm going to walk you through setting up a Blazor project using Clean Architecture. If you've ever wondered how to structure your Blazor apps to keep them maintainable, scalable, and, well, clean, you're in the right place.

Watch on YouTube 📺

Check out the full tutorial on YouTube to see everything in action 👇

video preview

Getting Started

First, let's fire up Visual Studio 2022 and create a new project. But instead of starting with a Blazor Web App right away, we're going to create a blank solution. Here’s how:

  1. Open Visual Studio and click on "Create a new project."
  2. Search for "Blank Solution" and select it.
  3. Name it something like CleanArchitectureBlazorExample.

This empty solution will be our playground where we'll build out all the layers of our architecture.

Setting Up the Project Structure

Next, let’s organize our solution by adding a Source (src) folder. This is where all our code will live. If you were going to add tests (not in this tutorial), you’d also create a test folder.

Now, let's dive into the Clean Architecture layers.

Understanding Clean Architecture

Clean Architecture is all about organizing your code into different layers:

  1. Domain Layer: This is the core of your app. It contains business logic and entities (like data models).
  2. Application Layer: Here, you'll have things like services and interfaces that use the domain layer.
  3. Infrastructure Layer: This is where you'll handle external stuff like databases, APIs, and file systems.
  4. Presentation Layer: This is the UI of your app, where Blazor comes in.

The idea is that each layer only knows about the layer below it. This keeps things clean and flexible.

Creating the Domain Layer

Let’s start with the Domain layer:

  1. Right-click the src folder > Add > New Project > Class Library.
  2. Name it CleanArchitectureBlazorExample.Domain.
  3. Remove the default Class1.cs file, and let’s add our first entity.

Here’s an example of what your entity might look like:

namespace CleanArchitectureBlazorExample.Domain.Entities
{
    public class Article
    {
        public int Id { get; set; }
        public string Title { get; set; }
        public string Content { get; set; }
        public DateTime PublishedDate { get; set; }
    }
}

This is a basic entity representing a blog article.

Creating the Application Layer

Next up is the Application layer:

  1. Right-click the src folder > Add > New Project > Class Library.
  2. Name it CleanArchitectureBlazorExample.Application.
  3. Just like before, remove Class1.cs.

Here, you might start implementing services or CQRS patterns. For now, let's keep it simple and add a Dependency Injection setup.

using Microsoft.Extensions.DependencyInjection;
namespace CleanArchitectureBlazorExample.Application
{
    public static class DependencyInjection
    {
        public static IServiceCollection AddApplication(this IServiceCollection services)
        {
            // Register your application services here
            return services;
        }
    }
}

This method allows us to add services from the Application layer to our Dependency Injection container.

Creating the Infrastructure Layer

The Infrastructure layer handles the gritty details like data access:

  1. Right-click the src folder > Add > New Project > Class Library.
  2. Name it CleanArchitectureBlazorExample.Infrastructure.

Again, we’ll set up Dependency Injection here:

using Microsoft.Extensions.DependencyInjection;
namespace CleanArchitectureBlazorExample.Infrastructure
{
    public static class DependencyInjection
    {
        public static IServiceCollection AddInfrastructure(this IServiceCollection services)
        {
            // Register your infrastructure services here
            return services;
        }
    }
}

Creating the Presentation Layer

Finally, let’s set up the Presentation layer using Blazor:

  1. Right-click the src folder > Add > New Project > Blazor WebAssembly App.
  2. Name it CleanArchitectureBlazorExample.WebUI.

In the Program.cs, we’ll hook everything up:

using CleanArchitectureBlazorExample.WebUI.Server.Components;
using CleanArchitectureBlazorExample.Application;
using CleanArchitectureBlazorExample.Infrastructure;
var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
builder.Services.AddRazorComponents();
builder.Services.AddApplication();
builder.Services.AddInfrastructure();
var app = builder.Build();
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseAntiforgery();
app.MapRazorComponents

This code adds the Application and Infrastructure services to the Blazor project.

Conclusion

And that’s it! You’ve set up a basic Clean Architecture with Blazor. This structure will make your app easier to maintain and scale over time.

If you’re interested in diving deeper into patterns like CQRS or the Mediator pattern, let me know, and I’ll create more tutorials on those topics.

Happy coding and have an awesome weekend!

Take care,

Patrick

PS: Need help understanding .NET & Blazor? There are two ways I can help you with:

  1. Check out the .NET Web Academy, which provides masterclasses and a supportive community of like-minded developers.
  2. I'm open to coaching. If you need specific help, reply to this email and we'll figure something out.

PPS: Would you like to sponsor this newsletter? Click here. 💌


.NET Web Academy

Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.

Read more from .NET Web Academy

Hey friend, The other day I found a bug in StackBuddy, an app I built. Normally I'd open it, file a ticket for myself, and move on. Instead I turned to my AI and just said, "log a dev ticket for that." And it did. A real ticket in my own bug tracker. Title, description, priority, the whole thing. I never opened the actual app. The thing that makes that possible is called MCP, Model Context Protocol. Ignore the name for a second. Out of the box, an AI can only talk. It writes and explains, but...

Hey friend, I don't really write code by hand anymore. I describe what I want, and the AI builds it. For a while, that scared me. If I am not writing the code, does everything I spent years learning still matter? Does my stack matter at all? If you are a developer right now, I would bet you have felt some version of that too. Here is where I landed. It flipped the whole thing for me. The other day I was debugging a slow app, talking it through with the AI. Would WebAssembly help here? Is it...

video preview

Hey friend, Lately I told an AI I’d see it in 7 hours, and went to bed. It was done in 2. Across two different projects. There’s this thing people call the night shift. You give an AI agent a pile of work, start it in a loop, and go to sleep while it keeps working on your real codebase. I tried it a month ago and could not make it work, the model just fell apart. But with the newest models, it works now. And the surprising part wasn’t that it ran all night. It’s that it ran out of work before...