Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Clean Architecture w/ Blazor 🔥, Blazor in the Industry 🚀, .NET Web Academy Enrollment Closing Soon 🎓
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.
🔥 Implementing Clean Architecture with Blazor on YouTube
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.
💻 Prefer Reading? Here's the Essence
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!
🚀 Blazor in the Real World: BurnRate's Growth Journey
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.
📚 .NET Web Academy Enrollment Closing Soon
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
.NET Web Academy
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend, This week, I built a working Blazor app from scratch in about 30 minutes. But that's not really the point. The point is how. Not by throwing a prompt at Claude and hoping for the best. But by thinking about architecture first, defining instructions and skills for the AI upfront, and then letting it implement while you stay in control and review the output. That's the difference between AI doing your job and AI doing the boring parts of your job. The video walks through exactly...
Hey friend, A year ago, I said AI coding tools weren't the future. I want to correct that. The distinction I missed: there's a real difference between vibe coding (copy-paste until it compiles, no understanding required) and skilled AI-assisted development (you own the architecture, AI implements it, you review the output). I was criticizing the first and accidentally dismissing the second. In 2026, skilled AI-assisted development is the professional standard. Not using these tools is now a...
Hey friend, We once spent five days in meetings debating a single delete button. Whiteboard sessions. A compliance guy nobody invited. A product manager who scrolled Slack for what felt like forever. And still no decision. Until Tom walked in on Monday morning, asked one question, and shipped it that afternoon. In this video, I tell the full story and walk you through the four questions that should end this debate on any team, in any codebase. Take care, Patrick P.S. We go deeper on exactly...