- App attach scripts are now digitally signed.
- Because of the previous, the configuration of package(s) for app attach has been moved to a separate JSON file
app-attach.json, which is then accessed by staging and registration scripts. In order to make adjustments (like changing the MSIX junction point path) edit the JSON file directly. Below is a typical file structure that is created (either from UI or from
- All MSIX app attach scripts have now constant names (for example
stage.ps1) and do not contain the name of the package anymore. This has the following benefits:
- It is easier to run them manually by just typing a few letters in Terminal window
- This is also now semantically correct, as the scripts are now effectively the same for all packages, since the configurable data has been moved to the JSON config.
- The content of the scripts for app attach has been generally improved in terms of code formatting, and a missing dismount routine (also not present in templates on MSDN) has been added to the
- Staging script had previously duplicated curly braces, which could cause an error returned by
mklink. The issue has been fixed in this version.
- Speaking of
mklink, its exit codes are now checked by the staging script. Non-zero exit code will break immediately.
- The dialog for certificate extraction can now trigger self-elevation (UAC) in case the checkbox for trusted store is checked.
- In the same wizard, a shield has been added to indicate possible elevation.
The app will be updated automatically in a few hours if you installed it from app installer file. New users can download MSIX Hero from the Download page.
Here is a visual comparison and update impact analysis of MSIX Hero 1.0.14 -> 1.0.16 upgrade. You can get similar results by exploring the options in the Ribbon > Tools > Update impact analyzer.