You can use the CLI manually to create a new MSIX package for your application.
The way that you do this is through commands with an elevated command prompt, with certain parameters that can be passed as command line arguments.
You need to have a path to the conversion template XML file that contains the package information in the settings for this conversion.
You also need to have the password for the virtual machine that is going to be used for the conversion environment. Your template file has to contain a virtual machine element and the settings.
There are various other commands and functions that you need to be aware of when it comes to using the command line in order to use MSIX manually.
Let’s take a look at some examples of commands and functions that you might need:
- Settings: AllowTelemetry [optional]: This enables telemetry logging for the tool.
- Settings: ApplyAllPrepareComputerFixes [optional]: This applies when all recommended prepare computer fixes are present.
- Settings: GenerateCommandLineFile [optional]: This function copies the template file input into the save location directory.
- Settings: AllowPromptForPassword [optional]: This prompts the user to enter the proper passwords.
- Settings: EnforceMicrosoftStoreVersioningRequirements [optional]: This forces the package versioning scheme for the Microsoft store.
- ExclusionItems:FileExclusion [optional]: This specifies the file to exclude for packaging
- ExclusionItems:FileExclusion:ExcludePath: This specifies an entire path that you should exclude for packaging.
- ExclusionItems:RegistryExclusion [optional]: You can use this function to exclude a registry key for packaging.
- ExclusionItems:RegistryExclusion: ExcludePath: You can use this function to specify an entire path to registry to exclude
- PrepareComputer:DisableDefragService [optional]: This disables the Windows defragmentation function while the app is being converted.
- PrepareComputer: DisableWindowsSearchService [optional]: This disables Windows search when the app is being converted.
- PrepareComputer: DisableSmsHostService [optional]: This function disables SMS host will the app is being converted.
- PrepareComputer: DisableWindowsUpdateService [optional]: This function disables Windows update while the app is being converted.
- SaveLocation [optional]: You can specify the save location of the tool here.
- SaveLocation:PackagePath [optional]: This is the path to the final MSIX package.
- SaveLocation:TemplatePath [optional]: This is the path to the file or folder for the CLI template.
- Installer:Path: This is where the application installers located
- Installer:Arguments: These are the arguments that you should pass on to the installer
- Installer:InstallLocation [optional]: This is a full path to your application’s root folder for the installed files.
- VirtualMachine [optional]: This specifies of the conversion will be run on a virtual machine
- VrtualMachine:Name: This provides the name of the virtual machine.
- PackageInformation:PackageName: The Package Name for your MSIX package.
- PackageInformation:PackageDisplayName: The Package Display Name for your MSIX package.
- PackageInformation:PublisherName: The Publisher for your MSIX package.
- PackageInformation:PublisherDisplayName: The Publisher Display Name for your MSIX package.
- PackageInformation:Version: The version number for your MSIX package.
- PackageInformation: MainPackageNameForModificationPackage [optional]: This is the main package name that is used when creating a modification package.
- Applications [optional]: The number of active application elements to configure the application entries.
- Application:Id: The App ID for your MSIX application. The ID used for the application entry.
- Application:ExecutableName: The name of the TXT file for the MSIX application.
- Application:Description [optional]: The App the description for the MSIX application.
- Application:DisplayName: The app display name.
- Capabilities [optional]: The number of custom capabilities.
- Capability:Name: The actual capability to add to your MSIX package.
You can get the MsixPackagingTool from the Microsoft Store or from the download section – Downloads