Essential Angular for ASP.NET Core MVC 3: A Practical Guide to Successfully Using Both in Yo

I completed an online course covering Angular, but I then wanted to know how to call a backend server with API calls. The online course used Firebase to save simple JSON data so was of no use to me.My requirements were authentication, user roles, C# MSSQL database back end, session data and cross-site forgery attacks.This book delivered the goods in all these areas. What I like about Adam Freeman is that he is clear, concise, and explains the main points. There is no waffle in this book.I skipped Chapter 10 covering Blazor as I have no intention of using it. But, by this point, Adam had explained enough to allow me to confidently change the files and skip the Blazor parts of his excellent source files. He has source for each chapter. After Chapter 10 I had to make sure I didn't add the Blazor related stuff, but I knew enough by then to know what to skip.The book develops two sides of a web application. The client side (Angular) and the server side (C# APIs).As Adam explains how these two interact, he has to add code to emphasise a feature and then remove it later as the app develops. So, you add code that would not be in a final application as the intention was to explain / demonstrate the interaction between the client and server aspects of the application. This is very well done.At the end of the book, you have an application that is served by the server "side" (C#) of the application.As designed, the JavaScript for the Angular (client) side of the app is sent to the client from the server "side" as it is integrated into the server side of the application.This is because the application, as designed, is using the same port (5001) on the server for both the angular ‘client’ and the C# ‘sever’.This is quite often not the case. Either a differnt port on the same server is used or the server is running on a differnet IP address / url.My only (very slight) criticism of this book is that Adam did not go further and explain how to totally split the application so that the Angular (client) and C# (server) parts of the application could run independently as is required in a lot of cases. Most importantly, mine!Perhaps a chapter 14 in a future release?For those who are interested, search for “Proxying to a backend server” and there is an article on the angular official website (angular.io/guide/build) to explain how to do it.Excellent book though. Well worth the money in my opinion.

Received much earlier that expected. Smells good

it covers in brief detail - doing a project involving angular 2 + with microsoft asp.net - in midst of reqding chapter 4 using data models

Very nicely explained step by step. Best for beginners.