At the 2022 Microsoft Build event, a new opportunity was announced for developers: the ability to upload MSI and EXE applications directly to the Microsoft Store.

As one of the most prominent programming languages in the world, Python is supported by many tools and modules. It is easy to learn and provides a nicely constructed code -- which opens the door for many solutions and endless possibilities.

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.

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.”

The MSI format is a widely recognized standard in the software industry for distributing software packages on Windows devices. The WiX toolset allows you to build MSI packages by writing XML files that describe components, registry entries, and other resources.

Developing in C++ means creating powerful and efficient applications. But once the development is done, how do we package such an app for the end users?

C# is a widely used programming language for developing various applications - from desktop apps to games and websites.

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.

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.

You often need to install additional components (known as prerequisites or runtimes) to your software product so it runs successfully on a machine. You must include the necessary prerequisites in the installer package for the application, ensuring that they are automatically installed on the machine when needed.

With the release of the MSI Packaging Academy after which you can get a certification that proves your packaging skills, I also thought to give you some of the most used application packaging interview questions, some of which I have asked different applicants during the years. These questions could give you a general idea of what is to be expected when you are going to your next interview and possibly could ease up your emotions.

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.

Software branding plays a fundamental role in distinguishing your product in the competitive market. Beyond functionality, your software's brand recognition is crucial.

Ever stumbled upon the message “Do you want to allow this app from an unknown publisher to make changes to your device”? You're not alone. This User Account Control (UAC) alert can be unclear, and potentially concerning for some users.

For many years, Windows was missing a handy feature that Linux users took for granted: an efficient package manager. This tool streamlines the process of installing, updating, and configuring software.

The confusion of dealing with unsigned drivers can sometimes disrupt your software installation process. Windows typically raises a red flag when such drivers come into play, triggering a warning message that it can't validate the publisher's credibility.