Hey Reader,
Today, we're diving into two burning questions that have been on a lot of your minds: How to implement Clean Architecture in a Blazor Web App and whether Blazor is viable in the industry.
In my newest video tutorial, I break down the essentials of setting up a Clean Architecture for your Blazor Web App in Visual Studio. We'll explore the four layers - Domain, Application, Infrastructure, and Presentation - and how they seamlessly integrate.
Here's what you need to know:
Start with a blank solution in Visual Studio and create a "src" folder for all your projects.
Begin layering by setting up three class library projects: "Domain," "Application," "Infrastructure". For the Presentation layer, kick off a new project with the "Blazor Web App" template, which will then be the starting project.
With Clean Architecture, each layer points inwards to ensure separation of concerns. A common industry practice allows the presentation layer to directly reference the infrastructure layer.
Ensure proper project referencing: Application refers to Domain, Infrastructure to Application, and Presentation to Infrastructure (taking the shortcut here).
For service registration, don't bunch it all in the Presentation layer's Program.cs. Add a DependencyInjection.cs file in both Application and Infrastructure layers with an extension method for the IServiceCollection. Invoke this in the Presentation layer's Program.cs.
That's it!
A lot of you have been asking if people really use Blazor for real work.
The story of BurnRate, run by .NET expert Robert McLaws, shows that yes, they do.
Instead of using complicated Excel sheets, BurnRate uses a smart "People Algorithm" with the help of Blazor and ASP.NET. This makes their website able to handle detailed financial stuff easily.
It's a great example of how Blazor is good for making reliable, ready-for-business apps. Check out how BurnRate uses Blazor here: BurnRate is fueling revenue success with Blazor.
Thank you immensely for your enthusiasm and support for the .NET Web Academy. Just a friendly reminder, enrollment is open for just one more week. Secure your place now at https://learn.dotnetwebacademy.com.
Have questions or need clarifications? Don't hesitate to hit reply to this email. I'm here to support with more tutorials if needed.
A big thank you to our incredible community and my Patrons for your steadfast support. You're the backbone of this newsletter and my channel. Stay safe, and remember, joy is found in coding! 💻
Take care,
Patrick
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend, Most developers use AI the same way: send a prompt, wait, repeat. It works. But it's slow. And it leaves a lot on the table. In today's video, I show you the workflow I switched to: running multiple Copilot agents in parallel, each working on a different part of the app at the same time. It feels less like using a tool and more like managing a team. And with vertical slice architecture, it just clicks. Take care, Patrick P.S. Want to set this up for your own projects or team? I'm...
Hey friend, Quick heads up. I'm hosting the next .NET Web Academy Monthly Live Session on Thursday, and I'd love to see you there. Last time we had some really good discussions and great questions from the group. This one will be the same format: open, interactive, no slides, no webinar vibes. I'll share my screen, we'll dig into whatever is relevant right now in the .NET and AI world, and you bring your questions, your current project, or just show up and listen. 📅 Thursday, April 30 CET:...
Hey friend, Starting a new Blazor project with AI integration can take a while before you even get to the interesting part. So I put together the Blazor AI Starter Kit: vertical slice architecture, authentication, and AI integration already wired up and ready to go. In this video, I walk you through exactly what's included and how it's structured. Download it, and you're building real features from minute one. Less setup. More building. Take care, Patrick P.S. The next Office Hours are coming...