commit ff092653971003856c128175be9ea7986c5eacbf
parent 444d230ff717752401d697c9db06c19bf1d2e966
Author: denelon <denelon@microsoft.com>
Date: Tue, 11 May 2021 14:27:32 -0700
Update export.md (#942)
Diffstat:
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/windows/package-manager/winget/export.md b/doc/windows/package-manager/winget/export.md
@@ -44,14 +44,16 @@ The driving force behind the **export** command is the JSON file. As mentioned,
The JSON file includes the following hierarchy:
| Entry | Description |
|-------------|-------------|
-| **Sources** | The repo that the the application is installed from. |
+| **Sources** | The sources application manifests come from. |
| **Packages** | The collection of packages to install. |
-| **Id** | The Windows Package Manager id used to identify the package. |
+| **Id** | The Windows Package Manager package identifier used to specify the package. |
| **Version** | [optional] The specific version of the package to install. |
## exporting files
-When the Windows Package Manager exports the JSON file, it attempts to export all the applications installed on the PC. If the **winget export** command is not able to match an application to an application from an available **source**, the export command will show a warning.
+When the Windows Package Manager exports the JSON file, it attempts to export all the applications installed on the PC. If the **winget export** command is not able to match an application to an application from an available **source**, the export command will show a warning.
+
+Note: matching an application depends on metadata in the manifest from a configured source, and metadata in Add / Remove Programs in Windows based on the package installer.
In the example below, you will see warnings for _reSearch_ and _Angry Birds_.
