General-use capabilities are specified by using Capability elements in your app package manifest. Restricted capabilities, which require approval for Microsoft Store submission and/or are generally only available to Microsoft and certain partners.Device capabilities, which allow your app to access peripheral and internal devices.General-use capabilities, which apply to most common app scenarios.Capabilities that provide apps with access to a sensitive resource are annotated by an asterisk (*) next to the capability scenario. For more info about accessing sensitive resources, see Security. Thus, it's important that your app doesn't assume a sensitive resource is always available. Privacy settings, managed by the Settings app, let the user dynamically control access to sensitive resources. These resources are considered sensitive because they can access the user's personal data or cost the user money. Some capabilities provide apps with access to a sensitive resource. Avoid declaring capabilities that your app doesn't need. It is important to know that when customers get your app from the Store, they're notified of all the capabilities that the app declares. For more information, see How to specify capabilities in a package manifest. You can declare general capabilities by using the Manifest Designer in Visual Studio, or you can add them manually. You request access to specific resources or API by declaring capabilities in your app's package manifest. Capabilities are used by UWP apps as well as other types of desktop apps that are packaged in an MSIX or AppX package for Windows. Capabilities must be declared in your Windows app's package manifest to access certain Windows APIs or resources, such as pictures, music, or devices such as the camera or the microphone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |