Inside MSIX
Demystifying MSIX Architecture, Development, Deployment and Troubleshooting
Latest posts
Activation via Command Line
Activation via Command Line We explored how to activate a packaged application by its AppUserModelId (aka AUMID), but that's not always convenient. Some tools only know how to run programs via a command line. But fret not. You can activate apps via a command line. AppExecutionAlias The most popular option is to activate an app via its declared AppExecutionAlias. A packaged app can define one or more app execution aliases. An execution alias behaves like a traditional command-line executable, but launching the alias actually activates the packaged application. Let's take the example we used to activate an ap...
Activation via AppUserModelId
An application can be directly activated by calling IApplicationActivationManager::ActivateApplication() with its Application User Model ID, also known as AppUserModelId or AUMID. For example, let's use a package with this fragment: This package's full name is . The suffix is the publisher ID derived from the package's publisher. Its package family name is therefore . The 's attribute is the application's Package Relative Application Id, also known as PRAID. An AUMID is a combination of the application's package family name and PRAID: Thus the card reader's AUMID is . We can now activate the applica...
Sparse Package
We recently discussed External Location and how it lets Windows find files referenced in but installed by some other (not-MSIX) installer. Many people call this kind of package a "Sparse package". Many even think sparse packages are the important feature, and External Location is a minor implementation detail. But...what is a sparse package? First, let's create one. HOWTO create a sparse package At its simplest, a sparse package contains and other footprint files, and no payload files.1 For example, here's a simple manifest for a HelloWorld application: The manifest declares , indicating it is intended ...
External Location
We talked recently about PackageVolume as one of the ways to stage packages. Let's turn our gaze to External Location, which plays a distinct role in MSIX, with similarities to - and important differences from - other options. Why is External Location? MSIX deployment provides a full-service software installation stack. The process is simple: collect your content, describe your package in an , and run makeappx.exe and signtool.exe to create a signed .msix to distribution and install. But...what if you already have a product with an existing installer? What if you need to extend your product with features uniq...
Activatable Extension Points
We often talk about "running an application", "launching an app", or "starting an app". This conjures up visions of spinning up a new process, giving the application life. For packaged applications, Windows has a specific term for bringing an application to life: activation. Bringing a packaged process to life involves more than ordinary unpackaged process creation. Windows calls this machine "activation". Activation does more than simply create a process. Among other things, it creates the new process with the appropriate package identity. Activation also verifies the package is in an appropriate state befor...
Is it MSIX? Part 3: Find Package and Application Identity with TASKLIST and PowerShell
We previously determined how to programmatically retrieve a packaged process' package and application identity. Now let's find MSIX package identity using existing tools. TASKLIST.EXE Using the packaged app from our previous example, we know the "image name" (aka executable filename) and that its PID (process ID) is 7664. lists packaged processes and their package names: That's overkill when we're interested in a specific process. We can use the (filter) option to limit the output to our target process: Or we can specify the image name and get the same result: The column is actually the package fu...
Is it MSIX? Part 2: Finding Package Identity with APIs
We previously determined how to tell if a process is packaged or unpackaged using Task Manager. Now let's find its package and application identity in code. Windows provides APIs to retrieve package and application identity for a process: If you prefer WinRT: Kernel mode What about kernel mode? Nearly all MSIX APIs require a user-mode caller. The Windows Driver Kit (WDK) provides RtlQueryPackageIdentity() and RtlQueryPackageIdentityEx() for querying package identity from a token. Tools? What about tools to do the same? Onward to Part 3... 1 returns but provides only the Package-Relative Application...
Is it MSIX? Part 1: How to Tell if a Process Is Packaged
Overheard in a recent conversation: Enterprise Administrator: "The ***redacted*** application is awesome, but it really should be an MSIX package." Microsoft Developer: "Ummm, it already is." That sparked another question: How can you tell if an application is packaged or unpackaged? Turns out there's a few simple ways to check. The key difference between packaged and unpackaged processes is whether they have package identity. Task Manager provides a convenient way to quickly see this: The list of processes now shows Package name: For example: In this example, ...
Footprint vs Payload files
Payload files Payload files are files stored in and delivered by the package. This includes your code, assets, and data, such as executables, DLLs, images, configuration files, and resources. For example: Content files The term content is sometimes used in MSIX-related APIs and documentation, but it does not provide as clean a classification as payload and footprint. For example, the Packaging API associates a content type with payload files. To avoid ambiguity, we'll use payload file when referring to files stored in the package. Footprint files Footprint files are package metadata and infrastructur...
