I really recommend this book for those that have a basic understanding of full stack, have built a basic site before and want to understand the nuts and bolts to what's happening so you can explain it properly.

I struggled in the beginning but now recommend this book to many, many people.

The book is very good. It covers just about everything there is to know about end to end full stack development.One thing I think is missing hough: unit testing.

As pointed out by other reviewers, this book is lacking in some key areas and as such I can't recommend it.

The book is titled "Hands-On...", which it most certainly is not. Early on, there are clear step-by-step instructions to follow along with, but these stop very quickly. After that, you're left scratching your head trying to piece together fragments of code and understand how and where they fit in to the application you are building. While there is source code available, it is for the finished solution which means you can't even deduce it yourself by looking at the relevant code for the chapter.

Another problem - the book is about ASP.NET Core which is a rapidly developing product. The book came out less than a year ago but much of the information is already out of date and consequently many of the examples don't work.

While the authors are clearly very knowledgeable, the book itself is impossible to follow along with, and consequently essentially useless. Very disappointing, as based on the blurb and table of contents this seemed like exactly what I was looking for.

Long story short - this book is a paperweight and I would not recommend buying it.

Practically no explanation; just essentially a collection of source code in book form. How can you learn anything from this? And the source code provided is for the "final" solution - there is no code for each chapter as you are suppose to build the app as you go along with the book. I would give this zero stars if I could.

It's not often I will leave feedback on a book - but this particular catastrophe cannot go unremarked. I literally have never read anything so confused and sloppy in my life.

This is supposed to be a BOOK. I purchased a BOOK, and yet the only way to get anywhere is to download the code from the publisher. Sections of code are shown in the book, but it's often unclear whether they are for demonstration if you want me to actually type them. When I do type them there's a good chance that they won't compile because you've completely failed to include all of the code I need to enter - entire essential methods are only in the downloadable code (page 107 for example: method CreateWebHostBuilder isn't printed in the book but the change you've asked me to make to Main won't compile without it!)

And even the downloadable code is faulty! The definition of the User class (not listed in the book at all) doesn't contain a UserID property, and this is very quickly detected when creating the initial migration on page 106; yet mysteriously your copy of the migration file does contain the UserID - how did you manage to create that migration?

The book covers the subject of routing twice, as it does for the process of installing of Postman.

Coding samples aside, the dialog itself is confusing, with far too many subjects piled on top of each other too quickly, with no space to analyse and digest what is being taught - this is after all supposed to be a teaching book. Also, subjects are introduced too early. For example, chapter 3 has a whole section on serving static files, but by chapter 5 (the pointer where I've given up with this book) I still have served ONE SINGLE static file. Why introduce the concept so early and muddy what your supposed to be doing: namely helping me learn this topic. The concept of static files, what they are, why they are need and how ASP.NET Core handles them should be introduced WHEN THE PROJECT ACTUALLY NEEDS static files.

As I said, I've given up on this book at chapter five; yet more code I'm having to pull out of the download, and again it won't compile. I want to learn ASP.NET MVC and this book is simply too much of a struggle.