Here are some of the errors I have found, that have you frustrated wondering if it is you or the book that is the problem:

page 30:
"entities.RSVPs.DeleteObject(dinner.RSVPs);" is wrong, should be "entities.RSVPs.DeleteObject(rsvp);"

page 35:
"[StringLength(265, ErrorMessage =" is wrong, should be "[StringLength(256, ErrorMessage ="

page 61:
The descriptions associated with the EventDate and ContactPhone fields in Figure 1-84 are inconsistent with the code. Adding a DisplayName attribute to the properties in your Dinner partial class will allow you to change the labels. This same problem is evident in other figures later in the book.

page 73:
The code for the create.aspx view will not create the look that is in figure 1-94. This is sorted out later when you implement a partial view based on the edit.aspx view, so don't worry about it.

page 89:
It is not clear from the code that the code on your edit view will now be like this:

<%: Html.LabelFor(m => m.Dinner.Title) %>

Instead of this:

<%: Html.LabelFor(m => m.Title) %>

i.e. Where "m." was present before it will be replaced by "m.Dinner." throughout the code in the view.

page 90:
As we are now using a DinnerFormViewModel in the view the TryUpdate in code snippet 1-53 needs to be changed.

"if (TryUpdateModel(dinner))" needs to be changed to "if (TryUpdateModel(dinner,"Dinner"))"

page 107:
You need to fully qualify the model you are inheriting from, i.e. you need to use this:

<NerdDinner.Helpers.PaginatedList<NerdDinner.Model s.Dinner>>

instead of this which is suggested in the book:

<NerdDinner.Helpers.PaginatedList<Dinner>>

Hi,

Please help me. My problem is :

I created private NerdDinnerEntities object 'entities'. There are two model classes in Entity i.e. Dinner and RSVPs. While implementing Insert/Delete method in DinnerRepository Class i stuck at entities.Dinner. because there is know Addobject() available neither the DeleteObject(). I couldnt even access entities.RSVPs instead intelissence shows entities.RSVPsSet

Help me out.

Thanks...

where to add PaginatedList<T> class in the project.

<NerdDinner.Helpers.PaginatedList<NerdDinner.Mod el s.Dinner> Will you explain Helpers come from where?

Hi, thats a very usefull errata, many thanks. One problem though on the page 61 tip, when I try to change the display names by adding a [DisplayName] attribute to the Dinner Partial class, when I start to type [DisplayName], it does not appear as an option in the intellisense?
I am using the System.ComponentModel.DataAnnotations reference and the [Required] and [StringLength] attributes work OK. Not sure what I am doing wrong?

You need to add a using System.ComponentModel to the Dinner partial class, then you can add the attribute, e.g. [DisplayName("Event Date")]

Helpers is a new folder you need to create that will contain the PaginatedList class.

On the top of page 89 - they say to change the Inherits attribute like so:
but shouldn't it be more like so?
Because on page 94, DinnerFormViewModel reappears on the screenshot - and it clearly states NerdDinner.Models.DinnerFormViewModel

I swear this book is a mystery novel.

Lol, well chapter 1 is for sure, in fact I never bothered finishing it all, however, once you have finished that hurdle the rest of the book is very good.

Another way to fix issue on page 89 is to use a Custom-Shaped ViewModel Class (which is mentioned in page 91).

Just modify your existing DinnerFormViewModel.cs to expose individual properties of Dinner:

If you expose just the properties needed for the view, you can still use
<%: Html.LabelFor(m => m.Title) %> in the view.

Also, since the view never directly references Dinner, you can make it private.


There are times where it is very useful to be able to shape the view like this (remember "separation of concearns"). Look at m.Title versus m.Dinner.Title. Think about this. What would happen if you swapped out the Dinner model with something new like FineDining model? You could then change the viewmodel and not change anything in the view. If needed you could "translate" property names like this:

Using this modified ViewModel has apparently fixed issue with page 90. So using "if (TryUpdateModel(dinner))" works now. And doesnt need to be changed to "if (TryUpdateModel(dinner,"Dinner"))"

btw, thanks to all who contributed here. It really helped me out.