Cascading Selection the MVC Way

Here are some things to note when using the AdventureWorks sample:

1. The sample application requires Visual Studio 2010 and the Xomega Framework binaries to use it.
   Unpack the framework binaries from the http://xomfwk.codeplex.com/releases to a folder
   Xomega.Framework and put this folder in the same directory where you have the AdventureWorks.sln file.

2. The solution file AdventureWorks.sln contains an Xomega model project AdventureWorks.Model.
   The model project is used to generate a large portion of the sample's code and the entity data model.
   In order to be able to use the model project you need to have Xomega.Net for Visual Studio installed.
   Please visit http://www.xomega.net to download it and for more details.
   You don't need to use this project to be able to browse and run the sample application though.
   You can ignore the project loading error and use the sample without the model project.

3. The sample application uses the AdventureWorks sample database from Microsoft. Before running the sample
   please visit http://msftdbprodsamples.codeplex.com and download and install the recommended version of the database.

4. The AdventureWorks database is considered to be running on a local SQL Server with windows authentication.
   If you install it on another machine or use different credentials, you need to update the App.config file
   in the AdventureWorks.Entities project accordingly.

5. The sample application can run both as a WPF, Silverlight or an ASP.NET web application.
   To run it as WPF application set the AdventureWorks.Client.WPF project as a start up project.
   To run it as Silverlight application set the AdventureWorks.Client.Silverlight.Web as a start up project.
   To run it as an ASP.NET web application set the AdventureWorks.Client.Web as a start up project.

6. The sample application handles all exceptions by displaying them in a message box or an Errors form.
   If you get XAML loading/initialization errors in Visual Studio when running it as a WPF application,
   you can press Continue instead of Break and you will get a detailed exception displayed
   that may help you determine the reason (e.g. DB connectivity problems).