MVVM Survival Guide for Enterprise Architectures in Silverlight and WPF

Errata type: Code | Chapter number: 1 | Errata date: 15 Oct 2012

In the Section, "Project View" you will need to also add the reference: using System.Windows.Controls.Primitives; This is because it is need to add the UniformGrid in the AddControlsToWindow() method. In the Section "Helpers" you have the following statement LoadProjects method: foreach (Project project in new DataServiceStub().GetProjects()) Shouldn't this be: foreach (Project project in new DataAccess.DataService().GetProjects()) In the method SetEstimateColor() you have the following statements: this.estimateTextBox.Foreground = _actualTextBox.Foreground; this.estimateTextBox.Foreground = Brushes.Green; this.estimateTextBox.Foreground = Brushes.Red; These statements should be: this._estimateTextBox.Foreground = _actualTextBox.Foreground; this._estimateTextBox.Foreground = Brushes.Green; this._estimateTextBox.Foreground = Brushes.Red; The project ProjectBilling.Monolithic will not compile without these changes.

Errata type: Others | Page number: 96 | Errata date: 29-10-2012

The third paragraph on the page should read:
Projects: An ObservableCollection class instead of:
Projects: An ObservableCollection class

Errata type: Others | Page number: 159 | Errata date:29-10-2012

These 2 lines of code under step 4 should be highlighted:
Tools.Add(new AToolViewModel());
Tools.Add(new BToolViewModel());

Errata type: Others | Page number: 171 | Errata date: 29-10-2012

In Step 3, it's helpful to note that this is also due to previously setting UpdateSourceTrigger=PropertyChanged on the textbox when we bound it to the company name in the user control's markup; removing this would break the change notification of EF as well.

Errata type: Others | Page number: 176 | Errata date: 18 Dec 08

Step 2 should be:
and a .NET reference from Northwind.Service to System.Data.Entity
instead of:
and a .NET reference from System.Data.Entityto Northwind.Data.

Errata type: Others | Page number: 196 | Errata date: 29-10-2012

In the second block of code on the page, in the GetCustomer() method, the logic is such that we find the customer from the _customers list then translate the DTO to a model object, however this logic is based on the (big) assumption that GetCustomers() is always called before the GetCustomer() method. It's better to do a simple check for the _customers list before searching it:
if( _customers == null)
GetCustomers();
This way, if we want to add some other functionality somewhere else on the program, where we don't necessarily retrieve the list of Customers first, we won't encounter an error while trying to retrieve a single customer instance.

Errata type: Others | Chapter number: 1 | Errata date: 26 Dec 12

In chapter 1, heading: History of presentational patterns=>Mvc, the following must be made public in order for the solution to work:
public Project Project { get; set; }
The code originally reads (in the book):
MVC Project Billing sampleModel
public Project Project { get; set; }
So MVC Project Billing sampleModel&rdquo should be a comment

Errata date: 11 Jan 2013

In chapter 2 “Introduction to MVVM”, Subchapter “WPF and Silverlight Enablers”, Section: “Dependency Properties”,the object herarchy for WPF should be: ( See also http://msdn.microsoft.com/en-us/library/system.windows.uielement(v=VS.85).aspx)

System.Object

   System.Windows.Threading.DispatcherObject

      System.Windows.DependencyObject

        System.Windows.Media.Visual

          System.Windows.UIElement
 
 

Errata type: Code| Page number: 103 | Errata date: 13-1-2013

IProjectsViewModel SelectedProject

should read:

IProjectViewModel SelectedProject

Errata type: Code| Page number: 11 | Errata date: 3-1-2013

The following must be made public in order for the solution to work:

 

public Project Project { get; set; }

 

The code originally reads (in the book):

MVC Project Billing sampleModelpublic Project Project { get; set; }

 

MVC Project Billing sampleModel” should be a comment 

Errata type: Code| Page number: 205-206 | Errata date: 30-4-2013

The Command.cs file as shown on p205 will not compile due to the method  
signatures of the Action<> and Func<> delegates.  Following are the  
(commented) errors and corrected lines.

//private readonly Action