I would like to have some more dialog with what is "best" practices. For example, subcontrollers, client side validation, etc.

I'm going to post things here as they come to mind...

- How to write a new Html helper.

ScottGu has done an awesome job writing the NerdDinner tutorial. Kudos!

Here's a list of suggestions I had in mind after reading the first chapter. I'll add more as I go along with my reading.

• Probably adding validations to latitude and longitude would have been overkill. However, in DinnersControllerTest.CreateTestDinners(), Latitude is set to 99 and the test passes. I don't know if Scott intentionally put it this way (explanation text would be nice). Otherwise, it would be helpful to have a more conventional value, i.e. between -90 and 90.
• Ask the users to download Site.css from the book's web site and copy to their local box before trying out the mapping stuff, or add a style to the map-div like so: <div id="theMap" style="position:relative">.
• Mention that Moq.dll needs to be 'Unblocked' (from file properties context menu) before a test can be run using Moq framework.

Regards

Routing is a bit confusing concept. The authors tackle it well. However, I think it might have been helpful if inbound routing would have been covered before explaining how outbound routing works. I'm referring to 'Under the hood' sections.

Named routes could have been explained a little bit more (Page 206).

More concrete examples would have been helpful.

In some of the later chapters, such as Chapter 7 on AJAX, it would be nice if the authors would show the code snippets (at least initially) in their context related to the application. They show code examples, but leave it up to the reader to figure out which pieces go in \Views\Home\Index.aspx and which pieces go in \Controllers\HomeController.cs, etc.

Similarly, in the downloadable code for each chapter, it would be good to have the actual files to download instead of (or in addition to) the "cut and paste" snippets.