Blueprints
Master Packager Blueprints is a database of packaging information from the Master Packager Team. It helps you package applications faster and learn how to create high-quality application packages.
In Master Wrapper, you can use a Blueprint to create a package from predefined application data instead of collecting the same information manually.
Blueprints are available only with a commercial license – Master Packager Pro or Master Packager Service Provider.
Why use Blueprints
- Start new packages faster with packaging information that is already prepared.
- Learn proven packaging practices from the Master Packager Team.
- Reduce manual research for installation actions, processes to close, and detection logic.
Supported data
Blueprints currently support the following application data. Review each item in Master Wrapper after the Blueprint is applied.
| Data | Details |
|---|---|
| General information | Application Name, Version, Publisher, and Language. See General. |
| App description | Description of the application. |
| Main application logo | Main logo of the application. |
| Actions | Install, Repair, and Uninstall actions for MSI installers. Install action for EXE installers. See Main Actions. |
| Processes to close | Processes that must be closed before the action runs. See Processes. |
| Detection method | Rule that detects whether the application is installed. See Package Detection. |
In the Script Editor, the actions added by a Blueprint are marked as Added by Blueprint in the Install, Uninstall, and Repair sections of the script.
Review and test before deployment
Information from Blueprints is provided for guidance only and may contain errors. Always review the generated package and test the installation, uninstallation, and detection on a test device before you deploy the package.