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.

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

When deploying with MSIX, the files and folders within the user's AppData directory (located under C:\Users\<user_name>\AppData) are written to a per-user, per-app location.

The Context Menu is undeniably one of the most useful shell extensions in Windows. This menu appears when you right-click on an object, like a file, folder, or icon, in Windows Explorer or File Explorer.

In our previous article, we simplified the steps of App-V 5 to MSIX conversion using MSIX Packaging Tool and Advanced Installer. We went even further and saw How to Automate the App-V to MSIX conversion.

In our latest article, we discussed App-V to MSIX conversion: Shortcut argument skipped during conversion. But that’s just the tip of the iceberg. The same goes for WorkingDirectory.

Automatically converting your App-V application to MSIX spares you from rebuilding them from the ground up.

If you're already familiar with the basics of publishing an MSIX application to the Microsoft Store, you're ahead of the game.

Branding an installation package plays a key role in today’s competitive digital landscape. It helps you differentiate your application in a crowded marketplace. Especially, for those in the application packaging industry, understanding how to brand an MSIX package is crucial to building trust and enhancing user experience.

In business, we often have to weigh the differences between expenses and true investments. Take the application packaging industry, for example.

Repackaging aWin32 app with Java dependencies as MSIX can often be challenging.

Application packaging is an ever-evolving domain, and MSIX has become the de facto choice for IT professionals and developers.When an application is packaged as an MSIX, it runs within a containerized environment that provides isolation and security.