|
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 👇 Getting StartedFirst, 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:
This empty solution will be our playground where we'll build out all the layers of our architecture. Setting Up the Project StructureNext, 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 ArchitectureClean Architecture is all about organizing your code into different layers:
The idea is that each layer only knows about the layer below it. This keeps things clean and flexible. Creating the Domain LayerLet’s start with the Domain layer:
Here’s an example of what your entity might look like: This is a basic entity representing a blog article. Creating the Application LayerNext up is the Application layer:
Here, you might start implementing services or CQRS patterns. For now, let's keep it simple and add a Dependency Injection setup. This method allows us to add services from the Application layer to our Dependency Injection container. Creating the Infrastructure LayerThe Infrastructure layer handles the gritty details like data access:
Again, we’ll set up Dependency Injection here: Creating the Presentation LayerFinally, let’s set up the Presentation layer using Blazor:
In the This code adds the Application and Infrastructure services to the Blazor project. ConclusionAnd 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:
PPS: Would you like to sponsor this newsletter? Click here. 💌 |
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend, I just released a new video and wanted to share it with you. Watch the video here 👇 I used GitHub Copilot to build a small Blazor weather app. It worked almost instantly and even used real API calls. At first glance, everything looked great. Then I opened the Razor file. All the logic was sitting in one place. UI, API calls, and business logic mixed together. It worked, but it was not something I would ship. In the video, I show how I fix this using a single refactoring prompt. I...
Hey friend, I just released a new video and I think you will enjoy this one. In the video, I ask GitHub Copilot to build a real mortgage app in Blazor. The app works. But the code is messy. All the business logic ends up in the UI. Fast results. Bad structure. Then I clean it up properly. Same behavior. Same output. Much better code using services, interfaces, and dependency injection. It shows why Copilot is powerful, but dangerous without rules. Watch the video here 👇 Enjoy the breakdown...
Hey friend, I just released a new video and I think you’ll enjoy it. In the video, I ask GitHub Copilot to build a .NET Web API using a short, vague prompt. The result works, but the structure feels random and messy. Then I run the same idea again with a stronger prompt that forces a clean structure. Feature folders. Vertical slice. Mediator. Fluent Validation. The difference is night and day. Watch the video here 👇 Enjoy the breakdown and let me know what you think. Take care, Patrick P.S....