| topic | languages | products | |||||
|---|---|---|---|---|---|---|---|
sample |
|
|
Shows how to get package info by using the Windows Runtime packaging API (Windows.ApplicationModel.Package and Windows.ApplicationModel.PackageId).
Note: This sample is part of a large collection of UWP feature samples. If you are unfamiliar with Git and GitHub, you can download the entire collection as a ZIP file, but be sure to unzip everything to access shared dependencies. For more info on working with the ZIP file, the samples collection, and GitHub, see Get the UWP samples from GitHub. For more samples, see the Samples portal on the Windows Dev Center.
Users acquire your Windows Runtime app as an app package. The operating system uses the info in an app package to install the app on a per-user basis, and ensure that all traces of the app are gone from the device after all users who installed the app uninstall it. Each package consists of the files that constitute the app, along with a package manifest file that describes the app to the operating system.
Each package is defined by a globally unique identifier known as the package identity. Each package is described through package properties such as the display name, description, and logo.
The sample covers these key tasks:
- Getting the package identity using Package.Id
- Getting the package directory using Package.InstalledLocation
- Getting package dependencies using Package.Dependencies
The sample covers these new tasks for Windows 10:
- Getting the package description using Package.Description
- Getting the package display name using Package.DisplayName
- Determining whether the package is a bundle package using Package.IsBundle
- Determining whether the package is installed in development mode using Package.IsDevelopmentMode
- Determining whether the package is a resource package using Package.IsResourcePackage
- Getting package logo using Package.Logo
- Getting publisher display name of the package using Package.PublisherDisplayName
To obtain information about Windows 10 development, go to the Windows Dev Center
To obtain information about Microsoft Visual Studio and the tools for developing Windows apps, go to Visual Studio
Conceptual
Reference
Windows.ApplicationModel.Package
Windows.ApplicationModel.PackageId
To learn more about sharing and the Windows.ApplicationModel.DataTransfer namespace, we recommend you take a look at the Sharing and exchanging data section of our documentation, which describes how sharing works and contains several how-to topics that cover how to share text, an image, files, and other formats. Our Guidelines for sharing content can also help you create a great user experience with the share feature.
For more info about the concepts and APIs demonstrated in this sample, see these topics:
- Sharing content target app sample
- Sharing and exchanging data
- How to share files (HTML)
- How to share files (XAML)
- How to share HTML (HTML)
- How to share HTML (XAML)
- How to share text (HTML)
- How to share text (XAML)
- Quickstart: Sharing content (HTML)
- Share data
- DataPackageView
- ShareOperation
- Windows.ApplicationModel.DataTransfer
- Windows.ApplicationModel.DataTransfer.Share
Client: Windows 10
Server: Windows Server 2016 Technical Preview
Phone: Windows 10
- If you download the samples ZIP, be sure to unzip the entire archive, not just the folder with the sample you want to build.
- Start Microsoft Visual Studio 2017 and select File > Open > Project/Solution.
- Starting in the folder where you unzipped the samples, go to the Samples subfolder, then the subfolder for this specific sample, then the subfolder for your preferred language (C++, C#, or JavaScript). Double-click the Visual Studio Solution (.sln) file.
- Press Ctrl+Shift+B, or select Build > Build Solution.
The next steps depend on whether you just want to deploy the sample or you want to both deploy and run it.
- Select Build > Deploy Solution.
- To debug the sample and then run it, press F5 or select Debug > Start Debugging. To run the sample without debugging, press Ctrl+F5 or select Debug > Start Without Debugging.