I often announce my new Pluralsight courses here, but this time it’s a bit of a special announcement: not 1, but 2 new courses, both covering REST in the recently-released ASP.NET Core 3! The first one is a beginner course: Building a RESTful API with ASP.NET Core 3. This is what you can expect:
In this course, you’ll learn how to build a RESTful API with ASP.NET Core 3. Creating a truly RESTful API is quite different from creating a regular web API, but in this course, Building a RESTful API with ASP.NET Core 3 , you’ll learn how. You’ll start by exploring how to interact with your API using the correct HTTP methods and status codes, and what method safety and idempotency are all about. Next, you’ll learn how to validate input that’s sent to the API, and how to implement common features like filtering and searching. By the end this course, you’ll know all about REST constraints, what the advantages are, and how to implement them when building your API with ASP.NET Core 3.
But REST is quite a big topic, so I created another course on it: Implementing Advanced RESTful Concerns with ASP.NET Core 3. As you can guess, this one covers the more advanced (and often pretty cool ;-)) stuff. Here’s the description:
In this course, Implementing Advanced RESTful Concerns with ASP.NET Core 3, you’ll learn how to implement advanced RESTful concerns with ASP.NET Core 3. Implementing these will lead to a better, more evolvable API. You’ll learn how improve your API with paging, sorting, and data shaping. You’ll also learn how to make your API more evolvable and robust with HATEOAS and advanced content negotiation, and how to deal with caching and concurrency. By the end this course, you’ll know all about REST constraints and you’ll end up with a level 3 RESTful API, which is the highest possible level of maturity.
Haven’t got a Pluralsight account? No worries, you can start with a free trial.
I hope you’ll like ‘m – happy coding! 
I enjoyed your Pluralsight course on RESTful API with ASP.NET Core. On your github site, I did not see the code for the controllers. Am I missing something–is the code out there?
Thanks,
David Johns
.NET and Angular Developer
I am learning a lot from your courses on RESTful API and started to build my own boilerplate. I just came across on an issue and I hope you could share some light.
I am getting an error of 422 Unprocessable Entity every time I will pass a null value to a property (boolean? type).
Basically I have a Get Method that accepts an Object as a parameter
[HttpGet(Name = APIConstant.RouteName.UserProfile.GetAll)]
[HttpHead]
public async Task Get(
[FromQuery]UserProfileViewModel.SearchCriteria searchCriteria,
[FromHeader(Name = “Accept”)] string mediaType) {}
UserProfileViewModel.SearchCriteria has this properties
public sealed class SearchCriteria : BaseSearchCriteria
{
public SearchCriteria()
{
DefaultOrderBy = nameof(ModelDTO.Username);
}
public string Email { get; set; }
public string Username { get; set; }
public bool? IsActivated { get; set; }
public bool? IsLocked { get; set; }
public bool? IsAdmin { get; set; }
}
Everytime I will pass a null value to any of the nullable bool, I get a 422 error. But if I set it to either true or false, it’s ok.
Thank you in advance.
Stay Safe!