In my experience, CustomActions can be difficult to add and set up, especially in MSI, often requiring reviewing lengthy documentation or dealing with unexpected failures or bugs. If you started your career prior to the App-V and MSIX era, you have probably come across various applications installers that required reverse engineering work.

In this article, you will learn how to configure and build an Advanced Installer Visual Studio Project(AIPROJ) from an Azure DevOps pipeline.

We can all agree that adopting new technology is not easy. In effect, it can be stressful for everyone.

In a previous article we had a look on how Environment Variables work with MSIX. We now know that in MSIX, Environment Variables are redefined as AppExecutionAlias.

TL;DR: Let's put it bluntly, you should never set a CustomAction to “Immediate” when you intend to change the system state.

Working with Azure DevOps pipelines can be a tedious task, especially if you have to perform updates on complex pipelines or make the necessary configurations to each of them in a short amount of time.

Ever wonder how an MSI registration ProductID is created?When installing an MSI, it registers on the system with a "strange" ProductID (different from regular ProductIDs) which is sometimes tricky to find. This is particularly challenging when you're trying to locate the package installer by its ProductID.

Nowadays CI/CD(Continuous Integration and Continuous Delivery) pipeline became a best practice for developers and DevOps helping them to manage the software process in a much easier and automated way.

A firewall is a network security system that can be found on any modern operating system. It's purpose is to act as a barrier against network-based intrusions, to monitor and control incoming and outgoing traffic following an organization's predetermined security rules.

Release management and version control go hand in hand when delivering quality software, whether you are a solo developer or part of a development team.

Managing an infrastructure doesn’t only require updating software, creating OS deployments, or applying GPOs (Group Policy Object).

In today's article, we're bringing a specific scenario into discussion and proposing the right solution to manage similar situations.

Environment variables are settings or paths that are set outside of a program and can be globally accessed by any software.

When building a new version of an installation package, you should pay attention not only to adding improvements but also ensuring a seamless upgrade to the old version.

If you have ever wondered how fonts are installed in an MSIX package or if you want to master all MSIX concepts, you landed on the perfect page. In the following article, we’ll see how to add and register fonts so your package will be more impactful.

Recently, in one of our previous articles, we covered how MSIX redirects user data to specific locations.

Recently, one of our users has asked us if it is possible to install, through Advanced Installer, a service under a Managed Service Account (MSA).

You've finished building your MSIX application, and it's time to share it with the rest of the world.

Although not necessarily common practice, there are some instances where you would want to prevent users from uninstalling specific MSIX packages such as monitoring software that is required to gather data from all employees.

MSIX Modification Package is a type of MSIX package format introduced by Microsoft with the goal of decoupling customizations from the main application. Launched with the release of their MSIX packaging format, the MSIX Modification Package is an MSIX package meant to store the customizations of the application.