u/Longjumping-Junket33in r/dotnet • Recommends
On “Would it be difficult to follow along a .NET Core 3.1 tutorial if I want to do it in .NET 6/7 ?”
#.netcore#asp.netcore#entityframework
102K subscribers • 4 videos on Hallway
Beginner. No background in the topic needed.
986K views6 years ago3 recommendations
Web developmentSoftware designHTTP, REST and GraphQLDesign patternsSoftware architecture
Les Jackson teaches how to build a REST API using .NET Core 3.1, covering MVC, the repository pattern, dependency injection, and Entity Framework.
In this full course, we show you how to build a full REST API using .NET Core 3.1. We’ll employ MVC, REST, the Repository Pattern, Dependency Injection, Entity Framework, Data Transfer Objects, (DTOs), AutoMapper to provide 6 API endpoints that will allow you to Create, Read Update and Delete resources. - Level: Beginner / Intermediate - My Book: apress.com/gp/book/9781484262542 - My other courses: lesjackson.net/ - Patreon Site (Exclusive Member Benefits!): patreon.com/binarythistle - Code on GitHub: github.com/binarythistle/S03E02---.NET-Core-3.1-MVC-REST-API --------------- INTRODUCTION - Course Overview - Application Architecture - API DEMO CODING PART 1 - FIRST 2 API ENDPOINTS (GET / READ) - Project Setup - Create our Domain Model (Command) - Build Our Repository Interface - Implement our Repository Interface (Mock Reposiory) - Create our Controller (CommandsController) - Create 2x API Endpoints - Using Dependency Injection CODING PART 2 - ENTITY FRAMEWORK & SQL SERVER - Architecture Checkpoint - Set Up SQL Server App Login - Entityframework Packages - Entityframework Toolset - Create our Database Context (CommanderContext) - Our Database Connecttion String - Register our DB Context in Startup - Create Migrations - Cancel Migrations & revist Command Model - Add Data Validations to Command Model - Create Migrations (Again!) - Run Migrations against Database - Add Data to Database - Revist Our Repository to use DB Context CODING PART 3 - DATA TRANSFER OBJECTS & CREATE ENDPOINT - Architecture Checkpoint - Why Data Transfer Objects? - AutoMapper Package & Startup Registration - Create our first DTO - Creating a mapping Profile - Updating Our Action Results to use DTOs CODING PART 4 - PUT, PATCH & DELETE API ENDPOINTS - Architecture Checkpoint - Updating our Repository for Creating Resources - Create a New DTO (for Creating) - Create 3rd API Endpoint to Create Resources - Use CreatedAtRoute to return 201 CreatedAtRoute - Add Annotations to DTO to avoid 500 Errors - Update Repository to Support Updates - Add a New DTO (for Updating) - Add 4th API Endpoint for Updating (PUT Request) - Update our AutoMapper Profile - Overview of PATCH - Install 2x packages to support PATCH - Update Startup - Update our AutoMapper Profile (Final Update) - Add 5th API Endpoint for Updating (PATCH Request) - Add 6th API Endpoint for Deleting (DELETE Request) FINAL THOUGHTS & ACKNOWLEDGEMENTS - Final Thoughts - Patreon Supporter CreditsWhat people say. Recommended as a helpful tutorial for beginners learning to build their first web API in .NET.
u/Longjumping-Junket33in r/dotnet • Recommends
On “Would it be difficult to follow along a .NET Core 3.1 tutorial if I want to do it in .NET 6/7 ?”
u/naming-is-hard3in r/dotnet • Recommends
On “help with Web API”
u/seamonkey123in r/dotnet • Recommends
On “Trying to build my first, very simple API. I feel overwhelmed and lost. Please help.”