For the past 10+ years, I have worked with various projects and types of organizations as an Application Packager. During that time, I have witnessed some "elementary" mistakes that could have been easily avoided by having a clear understanding of the end-to-end application packaging process.

MSIX packages have revolutionized modern application deployment, offering improved security, efficiency, and flexibility. However, even experienced IT professionals face challenges – whether in packaging, deploying, or debugging. Having the right tools and techniques is key to overcoming these obstacles.

MSIX flat bundle application packages are changing how applications are packaged and deployed.

Application dependencies are a common requirement in the packaging industry. With the transition from MSI to MSIX, we now have more options to declare and handle them.

MSIX is a modern application packaging format that simplifies deployment and updates. One of its key features is the ability to package registry settings along with the application, ensuring a clean and isolated setup. Key benefits include:

As we head into 2025, the application packaging world feels familiar—like a well-worn tool that still gets the job done. While there’s always talk of “the next big thing,” much of what worked in 2024 will keep working. Let’s break down what to expect.

The role of a software packaging engineer is often misunderstood. Is it just a small part of a bigger process? Is it a “one-man show”? And do you really need one in your company?

Whether you're a seasoned developer or just getting started, Windows Sandbox is designed to make your application installer testing process smoother, safer, and more efficient.

Back in the days of Windows XP and the early stages of application repackaging for enterprise needs, quality assurance teams often needed to verify that the repackaged MSI package had the same structure as the original installation package.

Windows context menus provide a quick way to access different commands, but as application complexity increases, these menus can become cluttered.

Digital Signing should be a formality for professionals. It’s been almost 30 years since the first software was digitally signed but we still have many users who don’t know how or why they should use a code signing certificate. We need it to protect their intellectual property and enhance the cybersecurity of their end-users.

Whether it's in-house applications, custom-made software, or applications from third-party vendors, there are times when we need to package them with a URL shortcut.

Today, we're exploring the WindowsApps folder that you find in Windows 10 and 11. This folder holds all the files for UWP (Universal Windows Platform) applications on your computer.

MSIX is a game-changer for software application distribution. However, it’s not all smooth sailing - there are challenges to face. A big one? Configuring your application.

With Microsoft's transition from MSI to MSIX, notable changes have emerged in application deployment, particularly in the software activation process.

With the release of version 1.2023.1005.0, the MSIX Packaging Tool has introduced an exciting new feature: PSF Fixups. This feature allows for the automatic injection of PSF fixups, eliminating the need for manual configuration. It applies to both converted packages (from App-V 5 to MSIX) and those created from scratch.

With the release of version 1.2023.1005.0, MSIX Packaging Tool has introduced a significant new feature: the Package Analyzer.

When you switch from using App-V to MSIX for packaging your applications, you'll notice a big change in how shortcuts work. MSIX doesn't use the old .lnk shortcuts StartMenu you might be used to. Instead, it uses something called “modern application entries.”

Microsoft’s guidelines for MSIX packages introduced a new approach to app configuration, in contrast with the MSI package format.

Microsoft introduced new guidelines for configuring apps deployed via MSIX packages, different from those for traditional MSI packages. These include the app configuration when the user first launches it. With MSI packages you could hand over the app configuration to the installer. With MSIX you have to add code to allow configuration at the app’s initial launch because the installation sequence is no longer customizable