Windows Phone Development for People in a Hurry

Recommended Project Layout for People in a Hurry

Project layout

Windows Phone SDK does not tell you how to organise your code. Here is a tried and tested skeleton filestructure that can be added to the pre-generated project structure

1. View
   1. Converters.cs
   2. UserControls
      1. MyUserControl1.xaml
         1. MyUserControl1.xaml.cs
      2. MyUserControl2.xaml
         1. MyUserControl2.xaml.cs
   3. ProfilesPage.xaml
      1. ProfilesPage.xaml.cs
   4. EditProfilePage.xaml
      1. EditProfilePage.xaml.cs
   5. OrdersPage.xaml
      1. OrdersPage.xaml.cs
   6. EditOrderPage.xaml
      1. EditOrderPage.xaml.cs
2. Model
   1. Profile.cs
   2. Order.cs
   3. DataSourceInterface.cs
   4. DataSourceInitialiser.cs
   5. DataSourceMigrater.cs
3. ViewModel
   1. AppViewModel.cs
4. SampleData
5. Includes
   1. WindowsPhoneToolkit
6. Images
7. AppConstants.cs
8. App.xaml
   1. App.xaml.cs

View/Model/ViewModel

• See MVVM for People in a Hurry for how to organise code into these directories

SampleData

• Expression Blend can create sample data. That data can go in the SampleData directory

Includes

• A space for included libraries ( .dll files)
• Pretty much every Silverlight Windows phone project will need the Windows Phone Toolkit (previously part of the 'Silverlight Toolkit', now a separate project)
• Create a separate folder for each library

Images

• A space for images that are included in the project
• For all images set the following properties in Visual Studio so they are included in the built project,
  • Build Type: Content
  • Copy to Output Directory: Copy if newer

Root directory

• Classes should be under the root namespace e.g. 'MyAppName'
• AppConstants is a static class with 'const' properties that are used throughout the app
• App.xaml creates an instance of the ViewModel class which can be referred to anywhere in the app as 'App.VM'