In our previous article titled "How to automate the MSI building using GitHub Actions", we saw how you can use Advanced Installer's own GitHub Action to automate the build of your MSI packages.

In this article, we will take a look at how MSIX technology handles log files whenever an installation issue occurs.

What's the most efficient way to perform quick edits to an MSI package?

With Intune, Microsoft made it easier to deploy MSIX/APPX packages in your infrastructure.

In 2018, MSIX was announced by Microsoft as the new universal package format for Windows 10 apps with the later support on desktop, mobile, and other Windows 10 devices.

We've received inquiries from users that encounter issues with the SCCM cache folder.

Digitally signing your application is not only mandatory, it is an essential step to making your software secure and trustworthy.

We are so proud to announce Alex Marin’s brand new work: the MSI Packaging ebook - visit the link to get your free copy.

A few days ago, we released a new version of Advanced Installer 18.8.

Sometimes we need to perform quick edits to our MSI packages without having to create a new project or going through the whole repackaging process.

During the installation process of WebApps, there are cases where users are asked to select an SSL certificate. This is because this certificate is used by the IIS elements.

We got a question in the Advanced Installer forum about the possibility of passing arguments to a service when the parameters are received from a configuration file, such as an .INI file.

Sometimes we need to have a single distribution package as an MSIX, which includes MSIX supported features along with MSI features that are no longer available (such as old drivers).

In the packaging industry, we're used to using application dependencies very often. And with the transition from MSI to MSIX, we have more options to declare and handle them.

There are scenarios where you need to change a file version programmatically with each launch. To achieve that, we will set an installer property that changes with each release and then uses its value within your installer.

One of the main things we need to consider when performing a Major Upgrade is how we will backup and restore our previous files and folders.

MSIX delivered Shared Package Containers to allow applications to share their files and registries, enabling classic Win32 apps to communicate with each other without changing any code.

If there's something we've mentioned over and over again about MSIX is that it requires digital signing. We have a diversity of resources regarding this topic, from why it is a good practice to include a timestamp when signing a package, to automating the whole digital signing process of MSIX Packages.

Announced in 2018, MSIX was presented by Microsoft as the universal package format. Although it may not be widely known, the MSIX technology retains the functionalities for translations and localizations of Universal Windows Platform or UWP Apps.

In order to allow a program to execute, you must first register its extension as a DLL or OCX.