Your application's installer is the very first direct interaction of users with your product. And, a positive first impression is essential for the success of any software.

The method to replace an existing configuration file varies depending on the application installer's format. For example, whether it's a vendor MSI from an Independent Software Vendor (ISV) or an EXE.

Self-healing, also known as self-repair, is one of the major benefits of the Windows Installer technology. In simple words, it ensures packages are secure and resilient by automatically checking and fixing them.

Did you package Notepad++ as an MSIX, and need to add extra plugins to it?

With the experience of unfortunate security breaches in recent years, the focus of making safe and reliable applications has increased in the software industry. This is why adding a digital signature to your application has become a must -- and for MSIX applications it is mandatory.

As we've emphasized before, we're big fans of MSIX technology here at Advanced Installer. It has brought more control to developers when it comes to their packages -- as it includes options for repackaging, rolling back updates and even downgrade scenarios.

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.

As software packagers, we know the struggle that comes with new technologies. And there's no need to sugarcoat it -- is downright stressful.

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.