• Visual Studio 2010 Express for Windows Phone Beta
• Windows Phone Emulator Beta
• Silverlight for Windows Phone Beta
• Microsoft Expression Blend for Windows Phone Beta
• XNA Game Studio 4.0 Beta

There have been some significant changes to the Windows Phone developer platform between the April CTP and the beta. Of note is the change to the navigation system which will terminate the application when it gets pushed into the background. I’ve already posted two articles that cover this in a bit more detail:

Windows Phone 7 beta- Who Killed My Application

Windows Phone 7 beta- Launcher and Chooser Tasks Cludge

In previous previews of Visual Studio 2010 the process started with you taking a copy of the default start page (ie StartPage.xaml) from C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\StartPages\en. Unfortunately this file no longer exists. Instead in their infinite wisdom, Microsoft has compiled the start page xaml into baml and embedded it into an assembly somewhere.

I figured, no problems, I’ll just start with the code sample that we already had working. Of course, there are missing and broken references. Even after fixing some of the references I noticed that the styling wasn’t the same as the default start page, so they must have added some polish to the start page since the code sample for the book was generated. I then decided to look further into where the start page had been placed. There were a number of dlls that I thought to be likely candidates for the start page:

• Microsoft.VisualStudio.Shell.10.0
• Microsoft.VisualStudio.Shell.UI.Internal
• Microsoft.VisualStudio.Shell.StartPage

Turns out it’s not in any of these assemblies (although it does reference controls and components from these assemblies as we’ll see later on). It’s located in Microsoft.VisualStudio.Shell.UI.Internal.resources.dll. I used RedGate’s .NET Reflector (http://www.red-gate.com/products/reflector) to trawl through these assemblies looking for start page references.

Now the challenge was that the start page has been compiled to baml – essentially a binary form of the xaml file. Luckily there is an awesome addin for Reflector called the BamlViewer that is available from CodePlex (http://reflectoraddins.codeplex.com/releases/view/1805). Download the addin and then go to View>Add-Ins to add the BamlViewer assembly to the list of addins.

Next, from the Tools menu select BamlViewer (only appears after the addin has been correctly registered). Locate the resource that you want to view, in this case StartPage.baml, and hey presto, there’s the xaml you’re after.

You can copy the xaml into a file called StartPage.xaml and then add this file into an empty WPF project. You’ll see that there are a bunch of references that you need to add – these are listed in the Grid element where it imports the namespaces:

<Grid xmlns=http://schemas.microsoft.com/winfx/2006/xaml/presentation 
xmlns:x=http://schemas.microsoft.com/winfx/2006/xaml
xmlns:sp=”clr-namespace:Microsoft.VisualStudio.PlatformUI;assembly=Microsoft.VisualStudio.Shell.StartPage”
xmlns:vs=”clr-namespace:Microsoft.VisualStudio.PlatformUI;assembly=Microsoft.VisualStudio.Shell.10.0″ xmlns:vsfx=”clr-namespace:Microsoft.VisualStudio.Shell;assembly=Microsoft.VisualStudio.Shell.10.0″ xmlns:d=http://schemas.microsoft.com/expression/blend/2008
xmlns:mc=”http://schemas.openxmlformats.org/markup-compatibility/2006″>

Make sure you add references to all of these assemblies – some are in the GAC, some of them you’ll need to locate under C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE. There are some other minor breakages that require a bit of tweaking – these are a result of the BamlViewer not quite getting the XAML correct that it generates (I’ve attached all the files to this blog post). The end result should be that you have a XAML page that will open in the designer of Visual Studio 2010. As you can see in the following image, the design experience doesn’t look the same as when the actual start page renders within Visual Studio 2010.

Now, to get your Start Page to display – Open the Options dialog (Tools menu), locate the Startup node under Environment and change the Customize Start Page to show your start page. Note that the xaml and csproj file have to be located under \Documents\Visual Studio 2010\StartPages for them to be available in the drop down list.

Restart Visual Studio and open the Start Page and you should see your custom page (although at this point it should appear the same as the default page).

Let’s add an additional tab to the start page. Open up StartPage.xaml and go to the end of the file. After the last closing TabItem tag add another TabItem element. For example the following code adds a Company tab (in bold).

            </TabItem>
            <!– Company Tab –>
            <TabItem Header=”Company”
                                     Style=”{DynamicResource StartPage.TabItemStyle}”
                                    x:Uid=”Company_Tab” >
               <Grid>
                  <Grid.RowDefinitions>
                     <RowDefinition Height=”Auto”></RowDefinition>
                     <RowDefinition Height=”*”></RowDefinition>
                  </Grid.RowDefinitions>
                  <TextBlock Foreground=”#E8E8E8″ 
                                              Margin=”15″ TextWrapping=”Wrap”
                                             x:Uid=”Information_Paragraph” > The Company has put a lot of effort into writing this custom Start Page so that you can quickly access information relevant to your job, the projects you are working on etc.
                  </TextBlock>
               </Grid>
            </TabItem>
         </TabControl>
      </Grid>
   </Grid>
</Grid>

When you save these changes and reopen the Start Page you should see your new tab appear.

In chapter 3 of Professional Visual Studio 2010 it also covers extending the start page by creating a WPF control and adding that to your start page – this is a good was to invoke behaviour when the user interacts with your page. This process works as described, except you need to deploy the dll that contains the controls to the C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies directory so that they can be referenced by the start page.

Start Page Template

One of the issues with using a single solution for building both Windows Mobile and desktop (or even web applications) is that when you do a build, by default, the Windows Mobile application will not only build, it will try to deploy to the device or emulator.  This can add a few extra seconds to every build so it’s not something you want happening on every build.

Luckily there is a quick way to disable this functionality: Right-click on the solution node in Solution Explorer and select Configuration Manager.  You will see that there is an additional column entitled Deploy and you’ll see that the mobile application has a check in this column. If you uncheck this your mobile application will not be deployed on each build.

There is one little gotcha here – if you are not careful you will experience a number of side effects:

• Build and run will NOT run the latest version of your mobile application.  It will build it but because you have not told it to deploy your application it will run the last instance of your application to be deployed to the device.
• If this is the first time you are running your application there is no previous version of your application on the device, so you will see a prompt similar to the following:

Unable to start program ‘%CSIDL_PROGRAM_FILES%\MobileApp\MobileApp.exe’.

The system cannot find the file specified.

There are two ways to address this:

1. You can force a deploy by right-clicking your mobile application project in Solution Explorer and selecting the Deploy option. Now when you run your application it will run the version you have just deployed.
2. You can create different build configurations – one for doing destop development and debugging, and one for doing mobile development and debugging.  In the former you can uncheck the build and deploy checkboxes for the mobile application.  In the latter you need to check both the build and deploy checkboxes for the mobile applications (note: you don’t need to deploy mobile class libraries so long as they are referenced by the actual mobile application as they will automatically get deployed along with the application).

Whilst the v3.5 toolset will install and register against Visual studio 2008 as well, you will need to update your wix projects to point to the v3.5 targets:

<WixTargetsPath Condition=" ‘$(WixTargetsPath)’ == ” ">$(MSBuildExtensionsPath)\Microsoft\WiX\v3.5\Wix.targets</WixTargetsPath>

The Extension Manager is just one of the many ways that Microsoft is opening up Visual Studio 2010 as a platform, not just a best of breed IDE for developers.

At this stage this feature doesn’t appear to work across files (ie selecting a method in one file and seeing it highlighted in other open files) or across assemblies (ie selecting a method call in the code of one assembly and seeing a highlight appear in another file from a different assembly).

• Jason Zander has a great post explaining a lot of the new functionality.
• Phil Haack gives the low-down on ASP.NET MVC with this beta.
• The documentation has also be released to MSDN.
• On Twitter everyone is discussing this using the #vs10 hashtag.

Unfortunately if you just want to open a single file or a project just to look something up you need to load up the entire Visual Studio IDE.  Here’s a tip from Dr Neil at nsquared solutions: Install the express skus (eg Visual Basic 2008 Express, Visual C# 2008 Express or Visual Web Developer 2008 Express) and use those to open these files.  These skus can be installed alongside the professional version and are much lighter wait.