Windows Phone App测试良好但提交后失败的可能性

1. 调用了诸如ScheduledActionService.LaunchForTest 之类只有在测试环境才能用的API。在提交后可能会闪退。
2. 写入 InstalledLocation 文件夹。安装文件夹在测试环境是可读写的，但是提交后就只读不可写了，而只能写入独立存储。
3. 把ProductId Hard Code了。Product Id 在提交后会变化。但是再次提交后不会变化，如果非要省事Hard Code的话，可以钻一个空子，第一次提交失败后，可以把生成的Product Id 填进Manifest文件和Hard Code。
4. (Windows Phone 7 only) In the Dashboard, inspect the list of Capabilities for your published app, and ensure that Marketplace didn’t remove any. This problem can occur owing to the various ways Marketplace audits the app in order to identify what capabilities are needed. The solution depends on which capability is missing. As a Windows Phone 7 example, for MediaElement to be detected, its name needs to exist in the xaml itself (x:name). Find more information about Capabilities here.
5. 提交了用于模拟器架构（X86）的App。提交时，一定要生成Arm+Release架构的App。
6. 要记得测试512MB的设备。
7. 打包了所有需要依赖的DLL。