A Cleaner Way to Build .NET Web APIs (No Controllers Needed!) 🤯


Hey Reader,

In my last video, I showed you how to build a CRUD app using Vertical Slice Architecture and controllers in .NET 9.

But… What if you could do the same thing - cleaner, simpler, and without all that controller clutter?

👉 That’s exactly what I show you in my brand-new video:

video preview

In this one, you’ll learn how to:

  • Use Minimal APIs instead of controllers
  • Keep your Program.cs neat and tidy
  • Stay fully organized with the Vertical Slice Architecture
  • Work with Carter, a super helpful library for modular endpoints
  • Still use CQRS + MediatR (but only if you want to)

It’s simple, modern, and super clean.

And yep, the complete source code is free to download (link’s in the video description).

If you're tired of bloated code or just want to try a different architecture style that actually scales, this is a must-watch.

And if you missed the first part (with the controller version), you can check that one out, too. 👇

video preview

Together, both give you a full picture.

Let me know what you think in the comments. I’d love to hear what you're building!

Take care & happy coding,

Patrick

P.S. Want to go further with real-world .NET & Blazor projects? Join me inside the .NET Web Academy and level up your dev skills with the community. Check it out here.


Patrick God

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

Read more from Patrick God

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...

video preview

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....

video preview

Hey friend, I just released a new video showing a better way to use GitHub Copilot in real .NET projects. Watch it here 👇 If you ever felt like Copilot starts strong but then your code slowly turns into chaos, you’re not alone. It happens to most developers when they start using AI without giving it the right guidance. In the video, I show you one simple file you can add to your project that keeps your code clean, structured, and consistent. No guessing. No random patterns. Just a clear...