We are working through the certification process on a Windows Phone 7 application and while we didn't hit it yet, I read via Shawn Wildermuth's post about how he failed once because he had referenced the Phone Notification assemblies and didn't provide a way to disable the notification. It was interesting to me because we have a common library for some of our reusables and that references and has calls to some of the phone notification APIs. Even though our application doesn't use the calls, because it references an assembly that does during the capabilities detection will mark the application as needing it. This occurs even if your manifest does not identify that as a capability that you use.
One solution to this is simply to refactor and make sure you don't reference it at all. In our particular application we do intend to use it in the future so we didn't want to remove the reference. Instead we simply add ...
Go to the complete details ...