Back in March 2018, Microsoft announced the MSIX packaging format and introduced Advanced Installer as the first recommended tool for creating MSIX packages.

PowerShell is, without a doubt, a powerful and commonly used scripting language for task automation and configuration management. However, sharing these scripts with non-technical users can be challenging, and that’s where converting a PowerShell script into an executable (.exe) file becomes useful.

As explained in other articles on our blog, MSIX treated the classical shortcuts differently.

The application packaging, deployment, and virtualization landscape is constantly evolving.

In today’s world, which is evolving at a rapid pace, new technologies are introduced into the market on a regular basis. Of course, not all technologies are adopted by the public, but some do leave their mark – either on a larger or a smaller scale – on the overall tech world.

When deploying applications, the architecture and packaging format you choose play an important role regarding compatibility, performance, and user reach.

MSIX is a modern packaging technology that provides reliable application deployment.

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.

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?