Well it looks like it was the culprit causing my app to have a Location and Networking Capability, when my app did not have a need for either.
I found this by taking a two headed approach.
- I built a Hello world application, checking on the capabilities at each step.
- Using the new Capabilities detection tool
- On my Vista 64 machine it was found here after installing it: C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.0\Tools\CapDetect
- In a Command window (Dos Window)
- goto the above directory
- And run the following
- CapabilityDetection.exe Rules.xml "C:\Users\David\Documents\Visual Studio 2010\Projects\HelloWorldWindowsPhoneApplication\HelloWorldWindowsPhoneApplication\Bin\Debug"
- I removed unnecessary items from the working app one by one to find running the above tool to see what the culprit was.
Microsoft's instructions can be found here: http://msdn.microsoft.com/en-us/library/gg180730(VS.92).aspx
I think Capabilities is a mis-nomer. In my case and I think most cases we would want our apps to have the minimum amount of capabilities our apps require. Why would a user want to buy/download an app that has a location requirement, that does not have a perceived need for it, a user would have privacy concerns.
Now I need to resubmit my apps.