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?

We are excited to introduce a powerful new feature in Advanced Installer: the ability to run .NET and .NET Framework code as a predefined custom action.

Have you just finished developing your application and created the installation package using Advanced Installer?

Winget is a command-line package manager created by Microsoft for the Windows operating system. It enables users to search for, install, update, and uninstall software applications using the command line or scripts instead of a graphical user interface (GUI).

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.

We are thrilled to introduce a groundbreaking feature in Advanced Installer - the ability to test your installation packages directly within Windows Sandbox.

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

Whether you're a seasoned IT professional or new to the application packaging industry, understanding the ins and outs of the process can be crucial.

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

Advanced Installer 21.0 is all about MSI packaging UI modernization. We are proud to introduce an innovative feature for enhancing the user interface of your MSI packages: MSI Embedded UI.

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.

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.

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.