> ## Content Index
> Fetch the complete content index at: https://blogs.remobjects.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Migrating a Metro app from Beta to Release Preview
- URL: https://blogs.remobjects.com/2012/07/05/migrating-a-metro-app-to-release-preview/
- Published: 2012-07-05T12:53:13.000Z
- Updated: 2018-08-22T06:17:42.000Z
- Author: jim
- Tags: #Import 2026-08-17 20:17

There were a few breaking changes to Metro apps when the [Visual Studio 2012 Release Candidate](http://www.microsoft.com/visualstudio/11/?ref=blogs.remobjects.com) came out. To develop for the latest version of Metro sing our tools, you will need the June 2012 Release or newer, which you can get from the usual places, including our [licensed downloads page](http://downloads.remobjects.com/?ref=blogs.remobjects.com) and [as trial version](http://www.remobjects.com/trials?ref=blogs.remobjects.com).

Once you have the June Release or a newer beta installed, you are ready to build Metro apps for the Visual Studio 2012 Release Candidate and Windows 8 Preview, but if you started working with the Consumer Preview of VS11, you’ll need to make the following changes:

- ***Remove public from your XAML Pages and App partial classes*** – You will get an error like ‘(E57) The type visibility for “app” does not match other class parts.’ Simply remove the **public** visibility modifier from the declaration in the interface section of your pas files. So instead of “type app = public partial class” it should say “type app = partial class”.
- ***Add a default language*** – You may get a warning like “(APPX1901) The DefaultLanguage property is either missing from the project file or does not have a value. The fallback language is set to the Visual Studio language: en-US.” You will need to open the .oxygene project file in your favorite text editor and add the line **en-US** in the first . The warning will then be removed.
- ***Recreate your certificate*** – Anytime you move a project from one machine to another you may find you need to recreate your certificate. You will know because you get a warning like “(APPX0107) The certificate specified is not valid for signing.” The fix is simple:
1. Just find the XXX\_TemporaryKey.pfx file in your solution (where XXX is the name of your project) and remove it.  
[](https://blogs.remobjects.com/wp-content/uploads/2012/07/Solution-Explorer-TemporaryKey.png)
2. If you try to build now, you will get the warning “(APPX0104) Certificate file ‘XXX\_TemporaryKey.pfx’ not found.” You need to create a new certificate: Double-click your **Package.appxmanifest** file in the solution explorer. From there, go to the *Packaging* tab.  
[](https://blogs.remobjects.com/wp-content/uploads/2012/07/Package.appxmanifest.png)
3. Click the **Choose Certificate…** button. From the *Choose Certificate* dialog, click the Configure Certificate drop down, and select \*\*Create test certificate…  
\*\*[](https://blogs.remobjects.com/wp-content/uploads/2012/07/Choose-Certificate.png)
4. Then, on the *Create Test Certificate* dialog, you can provide a Publisher ID or just click **OK**. Now you will have a new “XXX\_TemporaryKey.pfx” file and the warning will go away.
5. The Metro Style Apps Dev Center has [more information about valid certificates](http://go.microsoft.com/fwlink/?LinkID=241478&ref=blogs.remobjects.com).

There were a few other changes, but those will vary from app to app, depending on what you’ve done in the app. I’ve updated my [MetroExamples](https://blogs.remobjects.com/wp-content/uploads/2012/07/MetroExamples.zip) to work with the latest Release Preview and the June Release.