>>Tracy,
>>
>>I compiled it in VS2010 and it works fine.
>>
>>I still don't understand the PersonViewModel component. I could use some help with this.
>
>I'm assuming that it is the Commanding part that you don't understand?
>The WPF Button class has a Command property which takes an ICommand. In the PersonView.xaml the button is defined as:

<Button Content="Save" HorizontalAlignment="Right" Width="80" Command="{Binding Path=SavePersonCommand}"/>

meaning that it looks to the PersonViewModel SavePersonCommand property to supply this value.
>The ICommand interface only defines two methods : CanExecute() and Execute()
>Given an ICommand assigned to the Command Property the button has inbuilt behaviours:
>(a) it sets it's IsEnabled property based on the value returned by CanExecute() method.
>(b) when clicked it fires the Execute() method.
>
>Don't worry at this stage about the intricacies of the custom Delegate class - it's just a way of implementing the command outside of the normal visual tree. In this case the button looks to SaveCanExecute() to decide if it is enabled and runs SaveExecuted() when clicked (all automatically taken care of by the Command attribute)
>HTH,
>Viv

That helped. Thanks