问题
Background: I'm having trouble getting my app's new version accepted by the Windows store. They say that it crashes on launch. The app runs fine even when installed from the appxbundle file on my computer.
So I'm thinking maybe this has to do with the Desktop Extensions (for the UWP) that I've added. Perhaps I'm referencing the wrong version of that assembly. If the app is targeting version 16299 but min version is 14393 - which assembly of the desktop extensions should I include in the References? 14393? 16299? Or both (and the one between them as well)?
I'm tagging this Centennial as well even though it's a UWP app (from a Xamarin.Forms solution) because I needed the OK by the Centennial team for the Desktop Extensions. Maybe it has to do with that.
回答1:
If your app does not have the runFullTrust capability then you do not need Centennial approval. The Desktop Extension SDK just provides access to APIs that aren't necessarily available on other device families, like Xbox.
Your app can use the 16299 Extension SDK and still run on a 14393 OS as long as you don't use any newer APIs or you have light-up code in your app to detect whether APIs are available or not. You can use the ApiInformation APIs to detect whether certain WinRT APIs are available or not.
来源：https://stackoverflow.com/questions/49499011/windows-desktop-extensions-which-version-should-i-reference