Hello again 
I figured out a quick little change in the WMAppManifest.xml file that allows you to make your XAPs resume, rather than restart, when clicked on from the start menu.
Here's a demonstration:
So here's how it works:
In every WMAppManifest.xml file, located inside the XAPs, there's a line called "DefaultTask". In the Visual Studio IDE, there's little you can do with this line, but if you edit it post-compiling, you can actually do a lot of things. In this case, adding the term ActivationPolicy="Resume" to your DefaultTask will make the application resume the task, rather than replace it (default action). Here's an example:
Original:
Resumable:
This follows the same rules as the back button resuming, for example, if my dehydration hack is enabled, the code will resume instantly, and otherwise, it will resume with the usual "resuming..." message. It'll make sense
Should be fairly easy for you guys to figure out, and hopefully we'll see some developers integrate this directly into their code
For the end users, though, I've created a simple tool that does this patch for them, then deploys. Info and download over on my website:
http://windowsphonehacker.com/resumablexap
I'd say more, but I'm in a bit of a hurry. Let me know what you guys think, if you have any questions, etc.
Your friend,
Jaxbot
I figured out a quick little change in the WMAppManifest.xml file that allows you to make your XAPs resume, rather than restart, when clicked on from the start menu.
Here's a demonstration:
So here's how it works:
In every WMAppManifest.xml file, located inside the XAPs, there's a line called "DefaultTask". In the Visual Studio IDE, there's little you can do with this line, but if you edit it post-compiling, you can actually do a lot of things. In this case, adding the term ActivationPolicy="Resume" to your DefaultTask will make the application resume the task, rather than replace it (default action). Here's an example:
Original:
Code:
<DefaultTask Name="_default" NavigationPage="PivotPage.xaml" />Resumable:
Code:
<DefaultTask Name="_default" NavigationPage="PivotPage.xaml" ActivationPolicy="Resume"/>This follows the same rules as the back button resuming, for example, if my dehydration hack is enabled, the code will resume instantly, and otherwise, it will resume with the usual "resuming..." message. It'll make sense
Should be fairly easy for you guys to figure out, and hopefully we'll see some developers integrate this directly into their code
For the end users, though, I've created a simple tool that does this patch for them, then deploys. Info and download over on my website:
http://windowsphonehacker.com/resumablexap
I'd say more, but I'm in a bit of a hurry. Let me know what you guys think, if you have any questions, etc.
Your friend,
Jaxbot
