Files Excluded During Deployment

When deploying a Compatibility Package in any of the following modes:

• Deploy an Alchemy Compatibility Package to a User.
• Deploy an Alchemy Compatibility Package to a Machine.
• Deploy an Alchemy Compatibility Package to a Server.

Certain files in the package root directory are excluded from being copied to the target deploy directory. The excluded files are:

• Files with the exact name and extension “packaging-report.json“.
• Files with the file extension “.pfx”.
• Files matching the regex “usage.*.token$”.

If any of these files exist within the ProgData directory they will be copied.

Warning: It is strongly recommended to remove any packaging reports before initiating the licensing process. This step ensures that the package hash remains consistent after deployment. The .pfx and .token extensions are ignored from the Package Hash and so will not affect the ability to run your package.

For more information on licensing please see Licensing and Usage Reporting - Processes.

Example: Package Structure

To illustrate the concept of excluded files, consider an example package named "MyAppPackage" with the following files:

When this package is deployed to directory “C:\temp\MyAppPackage”, the deployed directory would contain the following files: