Hello Nate, I am following your course on Linkedin https://www.linkedin.com/learning/building-and-securing-restful-apis-in-asp-dot-net-core-2 and i don't quite get your chapter where you make the Links.
you presented so many methods with reflection that i kinda lost it.
Do you have any other resources to follow up ?
I find this course the flagship of building API's and you presentation is awesome.

Thanks for watching my course! I'm glad it was helpful. I don't have any other resources, sorry - other than the code that comes along with the course (and a similar open-source version: https://github.com/nbarbett....

Hi Nate, I've just finised your four-hour video course Building and Securing RESTful APIs in ASP.NET Core! on
https://www.linkedin.com/le....

What a great course. I will recommend this to anyone wanting to create a robust API.
Do you plan following this up with a FrontEnd(Client) Application to consume this API? I think it will enhance this course

In my quest to learn how to develop APIs I have seen others using a layered architecture in separate projects(Core, Infrastructure and Web-Front End). My Question:

1. Do you use the architecture used in this course for your enterprise project or you use a mixed of layered in a single project and separate projects.

Many thanks
Zak

Hi Zak, thanks for watching and commenting. I don't have any plans to create a follow-up course right now, but I'll keep that suggestion in mind.

I do like creating separation between the different layers of my application. I think it's critical to separate the different concerns properly. I don't have a strong opinion on whether it has to be separate projects (versus different namespaces in the same project). Separate projects does make the separation more strict, but unless it's a really big application it could be overkill. It's a fuzzy line in my mind.