Here we go again: a new Windows 8 version has been released (luckily, it’s the last one ) and we have to test our application against the RTM, to see if everything is working fine.
Luckily, this time the migration process is much easier than with the Release Preview: I’ve been able to run my applications on the RTM just by compiling them with the final Visual Studio 2012 release; when Release Preview was released, instead, I had to fix a lot of things, since there were a lot of breaking changes from the Consumer Preview.
In this post I would like just two highlight two important things to keep in mind.
Update the manifest file
Thanks to Daniele Bochicchio I’ve found that the Windows 8 manifest file contains a reference to the OS version which the application is compiled for. If you’re working on a project created with the Release Preview, the version number will be 6.2.0, while the RTM version number is 6.2.1. Unlucky, for old projects, Visual Studio doesn’t update it for you, so you need to proceed manually.
- In Visual Studio 2012 right click on the Package.appxmanifest file and choose View code.
- You’ll find a section in the XML file called Prerequisites.
<Prerequisites> <OSMinVersion>6.2.0</OSMinVersion> <OSMaxVersionTested>6.2.0</OSMaxVersionTested> </Prerequisites>
- Change the value 6.2.0 that is stored in both nodes to 6.2.1, so that it looks like this:
<Prerequisites> <OSMinVersion>6.2.1</OSMinVersion> <OSMaxVersionTested>6.2.1</OSMaxVersionTested> </Prerequisites>
And you’re done! This way you’ll be able to take benefit of all the WinRT changes applied to the RTM: otherwise, the app will run in a compatibility mode called Release Preview Compatibility Mode. You’ll app will pass the certification process anyway, but it’s better if we set from the beginning the right OS version.
If you want to go deeper about the RTM changes, take a look at this document published by Microsoft that lists all the changes between the RP and the RTM from a developer point of view.
Unable to activate Windows Store application: the app didn’t start
The first time you open your project with Visual Studio 2012 RTM and you try to debug it, you may occur in a strange error:
Unable to activate Windows Store application. The activation request failed with error ‘The app didn’t start’
In this case the solution is simple: close Visual Studio, delete the bin and obj folders inside your project’s folder, open it again with Visual Studio and launch it. This time it will start successfully!
If still get the “The activation request failed with error ‘The app didn’t start’” you may also try to delete the assembly bindings in the app.config. NuGet may automatically add it in some cases.
app.config file does not exist in my UWP Project. then how to remove that file?
Hello, this post is quite old and it refers to Windows 8 applications. UWP apps for Windows 10 don’t have an app.config file by default.