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.

It is commonly known that MSX technology comes with a set of limitations that most of the packagers must deal with, in spite of all its benefits.

Applications behave differently when running within an MSIX container. For example, you cannot set a non-executable file as a target for your application by default.

When Win32 applications run inside an MSIX container, they behave differently than when they are installed natively. Because of that, we come across errors in the operations we often perform.

Advanced Installer was the first application to fully support MSIX technology – and we truly believe in its power.

You’ve finished building your MSIX application, and it’s time to share it with the rest of the world.

MSIX packaging is a modern solution for deploying applications on Windows devices. However, if you want MSIX-deployed apps to support auto-updates via .appinstaller file on Windows Server, you have to manually install the App Installer Tool.

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.

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.