Beyond Basics – RESTful API with ASP.NET Core and EF Core
$19.99 $14.99Track price
Thank you for checking out my course.
So what is the course all about? As the name – “Creating RESTful API with ASP .Net Core 3.0 and Entity Framework Core” implies, we will dive into building an API using REST principles. We’ll use Entity Framework Core for persisting our data in database and ASP .Net Core 3.0 framework for interacting with it.
What will we build.
Simple answer is CRUD API that uses GET, POST, PUT, PATCH, and DELETE verbs to manipulate the resources for music Bands and the Bands Albums. However we’ll do so much more than that! We will also let our API to filter and sort resources; apply pagination to limit the number of resources per page; implement Data Shaping to allow the user specify which properties should be returned and which ones can be ignored; we’ll let the user to create a collection of resources with a single API request; support Json and XML; add Upserting, which is creating a new resource with update, if the resource doesn’t yet exists, and we’ll implementing it both for PUT and PATCH verbs; we’ll implement input validation, both with IValidatable Object and we’ll also create a Custom Validation Attribute; we’ll have a close look at status codes and make sure they adhere to REST principles; we’ll use OPTIONS and HEAD verbs and explore how and why to use them; and we’ll add custom headers to our responses. Of course, we will work heavily with Entities and Data Transfer Objects (DTO). And all of that will be implemented via Repository Pattern.
Instructor Details
Courses : 12
Specification: Beyond Basics – RESTful API with ASP.NET Core and EF Core
|
5 reviews for Beyond Basics – RESTful API with ASP.NET Core and EF Core
Add a review Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Price | $14.99 |
---|---|
Provider | |
Duration | 9 hours |
Year | 2020 |
Level | All |
Language | English |
Certificate | Yes |
Quizzes | No |
$19.99 $14.99
Romp11 –
Greatest course ever about API, thank You so much ! You are giving me so much knowledge and explaining everything like a charm ! Course beyond my expactations ! P.S. When i finish this course i’m going to buy next one from You about .net web app Cheers !
Florian Rubel –
The author pushes you through the basics of the api development in C# with .NET Core really good and teaches you how to prevent duplicate code in an amazing way. I totally loved this cource and can absolutely recommend it. The concepts that you got teached are way better than what I have seen in other courses so far. However, there are two downsides: 1. The advanced topics are really advanced and I had a lot of struggle to understand them. You have to learn advanced topics in C# to really understand them. 2. I am missing 4 Sections in this cource, that I think should be added, even with a higher price tag: Authentication/Authorization, Environment Configuration (dev, prod), Api Documentation (with Swagger?) and Deployment.
Marina Landisberg –
Everything is reproducible so far. Was a bit lost when was looking where localDB database was created certainly not within project folder, but later found that database was after all available, but in user folder (in my case it happened to be C:UsersUser)
Javier Carmona Gallegos –
I was expecting to use Visual Code, but I think for now it’s ok with Visual Studio, I already know how to replicate all the project on Visual Code
M Kelly –
This course is well worth it; so far Pavol has taken great care to explain every feature he includes, and he shows different ways of doing things. My only dislike so far is AutoMapper; as an experienced programmer I personally do not find any value in AutoMapper; I am not a fan of Black Box, I like to see all the logic. I also prefer generic repositories that are implemented using asynchronous methods. I am just over halfway through the course and I am thoroughly enjoying Pavol s lectures. I definitely recommend this course. Brilliant! C# is my favourite programming language but I do not like the dynamic feature even though I know the reason for it inclusion (Office and other related dynamic interoperability), and dynamic was useful for the data shaping but I like to fight against any form of non strongly typed languages; this is just my bias, my roots are in strongly typed classical OOP languages. Thanks Pavol. If you can I would like to see your take on Blazor. To me, it’s a pleasure to work with.