Version 17.2 of Advanced Installer brings you more than 20 features and enhancements ready to be discovered.

To help with the MSIX transition, Microsoft has released the Package Support Framework (PSF) - an open-source framework that enables you to apply runtime fixups for issues that might appear when migrating legacy applications that you don’t have the source code for.

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.

We have good news! Advanced Installer 17.1 comes with Digital Signature support for PowerShell scripts - you can now digitally sign PowerShell scripts to enhance your enterprise security policies.

Automation. A word heavily used around industries, especially the software one. A word that arouses great interest for every manager, service, or business owner.

Every new MSIX package we build allows us to learn more and improve the tools we build. The whole Advanced Installer team got involved.

Although it’s a rare scenario - you might run into the situation where you need to continue the installation of a certain application after reboot. We are talking about a silent installation that doesn't require admin rights or any input from the user.

As a standard, Advanced Installer automatically creates the components when generating the product package. The automatic process respects a strict set of Windows Installer rules, together with a series of best practices we have gathered from our customers during the years.

Since 2018, when Advanced Installer was named The Microsoft Launch Partner for MSIX technology, we've worked on setting its foundation and continuously bringing you powerful tools - all with the goal of making your job easier.

We learned in How does Files Redirection work with MSIX that user data files, either from the project or created by executables, are automatically redirected to: %localappdata%\packages\PublisherName.AppName_hash\LocalCache.

Every software packaging department has its own rules when it comes to MSI - whether we talk about naming convention (package naming, product naming) or package description and comments.

We plan a full year of MSIX concepts ready for you to master. Explore our latest feature, Windows Services for MSIX - install, control, and customize the newly added service with only a few clicks. For a quick demo, check the video below.

In this article, we go through:

Lessons I have learned from making many mistakes in my enterprise software packaging newbie (and not only) years.

Are you a PowerShell fan? Check this awesome feature that allows you to edit an MSI or simply create an MST file.

In our IT Pro world, the best practice we have in place regarding app deployment is that all applications are installable per machine. No matter if it’s an MSI, EXE, or other custom types of installers.

The purpose of this article is to show you how redirection works and how you can add your user files in the project using Advanced Installer GUI.

In this article, we went through the process of building an MSI package for an Electron application and we have delved into how to parametrize a setting within the newly created Electron MSI package.