Hunt Blog

I am just getting started with the MVVM Pattern.  I have been accumulating information that is starting to spill over. I figured it was time to consolidate the information into a post.

Introduced in 2005 by John Gossman, the Model-View-ViewModel pattern enables loose coupling between the view, its related code, and the model, resulting in increased testability, flexibility, and maintainability of the application.

Jason Dolinger, Senior Engineer at Lab49 has an excellent presentation (1hr 30min) on the evolution of building MVVM applications from a classic WinForms perspective to using MVVM as well as a blog post that contains links to the original source code for the presentation.

In his presentation, Jason ignores the 'Model' component of the MVVM pattern. Josh Smith and Craig Shoemaker's MVVM video for WPF addresses the relationship between the Model and ViewModel (as well as other things).

• Introduction to Model/View/ViewModel pattern for building WPF apps by John Gossman
• WPF Apps With The Model-View-ViewModel Design Pattern by Josh Smith.
• 5 Minute Overview of MVVM in Silverlight by John Papa.
• MVVM Design Pattern for Silverlight Applications by Jonas Follesoe.
• Understanding Routed Events and Commands In WPF.
• CodeProject Articles by Josh Smith.
• (Data)Model-View-ViewModel Pattern Blog Series by Dan Crevier.
• MVVM Blog Series by Kent Boogaart.
• MVVM Foundation on CodePlex.
• Ask Dr. WPF
• Exploring a Model-View-ViewModel Application; WPF Password Manager, Cipher Text.
• M-V-VM TRAINING DAY SAMPLE APPLICATION AND DECKS.
• MVVM Blog Posts by Karl Shifflett.
• VMWorkshop - The VM Workshop is a simple reference application demonstrating the Model View ViewModel (MVVM) and Presentation Model pattern in a number of different UI platforms.

1. ProductName - This will identify each instance uniquely. I would recommend indicating each instance by its target environment to help users know which one they are running as well as knowing which one they are uninstalling if using Add/Remove Programs. e.g. <Product Name> - Development
2. SignManifests - This was the one parameter missing from Kavinda's post that was forcing the value for publicKeyToken (a part of the application identity that must be unique to allow the applications to run side-by-side) to always remain at a value of "0000000000000000".
3. ManifestKeyFile and ManifestCertificateThumbprint - These values are what are used to actually sign the manifest. These were what Kavinda was correctly noting in the article.

The Result

I have one exec task in my nant script that takes in parameters that are set by running a target specific to the intended environment:

<!-- deployment properties -->
<property name="publisher.name" value="My Company Name" />
<property name="publish.output.base.dir" value="\\UNCLocation\Deployment\ProductName" />
<property name="product.name.base" value="ProductName" />
<property name="product.name" value="SET_BY_TARGET__DO_NOT_CHANGE_HERE" />
<property name="build.label" value="SET_BY_TARGET__DO_NOT_CHANGE_HERE" />
<property name="publish.output.dir" value="SET_BY_TARGET__DO_NOT_CHANGE_HERE" />
<property name="manifest.certificate.thumbprint" value="SET_BY_TARGET__DO_NOT_CHANGE_HERE" />
<property name="manifest.key.file" value="SET_BY_TARGET__DO_NOT_CHANGE_HERE" />

<target name="deploy.to.dev">
    <property name="publish.output.dir" value="${publish.output.base.dir}\Development\" />
    <property name="manifest.certificate.thumbprint" value="003dd8c1fca443b398d240a54a7e47f2" />
    <property name="manifest.key.file" value="certificates\development.pfx" />
    <property name="product.name" value="${product.name.base} - Development" />
    <call target ="deploy.common" />
</target> 

 <target name="deploy.common">
    <exec program="MSBuild.exe"  
              commandline='MyProject.csproj /target:rebuild;publish /property:ProductName="${product.name}";
                                     PublisherName="${publisher.name}";
                                     SignManifests=True;
                                     ManifestKeyFile=${manifest.key.file};
                                     ManifestCertificateThumbprint=${manifest.certificate.thumbprint};
                                     BootstrapperEnabled=True;
                                     CreateDesktopShortcut=True;
                                     UpdateRequired=True;
                                     UpdateMode=Foreground;
                                     MinimumRequiredVersion=${build.label};
                                     AssemblyVersion=${build.label};
                                     ApplicationVersion=${build.label};
                                     Install=True;
                                     Configuration=Release;
                                     Platform="Any CPU";
                                     OutDir=..\..\..\${build.dir\;
                                     OutputPath=${publish.output.dir};
                                     PublishDir=${publish.output.dir};
                                     PublishUrl=${publish.output.dir};
                                     InstallUrl=${publish.output.dir};
                                     UpdateUrl=${publish.output.dir}
                                      /nologo /verbosity:quiet' basedir="${framework.dir}"/>
</target>

There are a few extra items in there that force this application to be installed locally as well as always remain at the latest version that are not applicable to this post, but I am leaving them in there for completeness.

1. Uninstall SQL Server 2008 Express installed by the Microsoft Web Platform Installer and, instead, download Microsoft SQL Server 2008 Express with Advanced Services and install it as per this SQL Server Development Center Forum thread (this installer gives you a LOT more options than the web install!!!). Though, in hindsight, I figure I could have likley simply installed Cumulative update package 2 for SQL Server 2008 as per the FIX: Full-text search functionality does not work in SQL Server 2008 Express Edition article. I did not test just installing the cumulative update. YMMV. 
2. Folow the instructions from the How to: Enable FILESTREAM MSDN article (this option can be enabled during the installation of Microsoft SQL Server 2008 Express with Advanced Services).
3. Because the installer failed, (see fail messag below) I downloaded the zip file and edited the install<X>db.sql script located in the folder of each of the different databases you can install. The things I had to edit:
• :setvar SqlSamplesDatabasePath (line 39) (to "C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\")
• :setvar SqlSamplesSourceDataPath (line 40)  (to "C:\<unzip folder>\Tools\Samples\" e.g. "C:\temp\adventureworks\Tools\Samples\")

           Then I ran the script from the command line by executing sqlcmd -S <machine name>\SQLEXPRESS -i instawdb.sql

Adventureworks successfully installed... finally!

AdventureWorks Installer Fails:

1. After selecting database instance, the next button is not enabled until you select the database instance, then click back, then click next to come back to this screen.

     2. And then receiving the ended prematurely dialog with the gracious opportunity to finish with no further information.

Licensing : 

• Per developer @ $995.00 USD Renewal @ $495.00 USD
• Per developer @ $1490.00 USD with one year of priority phone, 24-hour chat and rapid response online support. Renewal @ 749.00 USD

Product: Essential Studio WPF Edition - Online Demo

Includes: Data Grid, Tools - Ribbon/Docking/Editors/Menus/MDI, Chart, Diagram, Editors - with highlighting, Gauge.
Licensing : 

• Per developer Binaries only: @ $995 USD
• Per developer with Source Code: @ $1295 USD

Product: UI ControlSuite .NET Enterprise edition

Includes: Slideshow, Control resizer, ScrollViewer and ScrollBar, Grid and TreeListView, Ribbon, UI Virtualizing WrapPanel, Content flip / rotation capable Content control, Tab/Navigation, ListBox, and Color picker.

Licensing : 

• Per developer @ $249.00 USD
• Per developer @ $299.00 USD with source code
• Per developer renewal fee @ $179 USD

Product: Nextwave Suite 2.5 for WPF - Dashboard Samples

Includes: Chart for WPF, and Nextwave Gauge for WPF

Licensing: 

• Per developer @ $1,169.50 USD
• Per developer @ $1,451.50 USD with source code
• Site License @ $2,339.50 USD
• Site License @ $2,621.00 USD with source code
•  Per Developer Renewal @ 179.00 USD
• Site Renewal @ 1,169.00 USD