u/Tapifin r/dotnet • Recommends
On “Managing Minimal APIs”
link to this video
I found this video handy when it came to refactor to minimal api's
0:00 / 0:00
Fix Your Controllers By Refactoring To Minimal APIs
Milan Jovanović
169K subscribers • 11 videos on Hallway
- Recommended by 2 people: 2 in engineering communities.
- Presented by Milan Jovanović
Intermediate. Assumes working knowledge.
66K views3 years ago2 recommendations
Web developmentSoftware designHTTP, REST and GraphQLRefactoring and legacy codeC# and .NET
Milan Jovanović demonstrates how to refactor an ASP.NET Core application from traditional controllers to Minimal APIs using static methods and groups.
Get the source code for this video for FREE → the-dotnet-weekly.ck.page/controllers-minimalapis ☄️ Master the Modular Monolith Architecture: bit.ly/3SXlzSt 📌 Accelerate your Clean Architecture skills: bit.ly/3PupkOJ 🚀 Support me on Patreon to access the source code: patreon.com/milanjovanovic Minimal APIs were added in .NET 6 and keep improving with each new version. Minimal APIs are easy to work with, more lightweight than controllers, and perform better. But how do you move from Controllers to Minimal APIs? That's what I will show you in today's video. Join my weekly .NET newsletter: milanjovanovic.tech Read my Blog here: milanjovanovic.tech/blog Chapters Controllers are dinosaurs Going from Controllers to Minimal APIs Using static methods for endpoints How to use Groups to manage endpoints Exposing endpoints on the API level Strong typing for Minimal APIsWhy it's here
2 people recommend thisWhat people say. Recommended as a handy guide for refactoring .NET controllers to Minimal APIs.
u/_v3nd3tt4in r/dotnet • Recommends
On “Controllers vs. Minimal APIs Which Do You Prefer and Why ?”
I'd suggest looking up some videos and reading msdn. Some video authors I would suggest is:
link to this video
link to this video
link to this video
link to this video
link to this video