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.

In this article, we go through:

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.

When it comes to registry inside the MSIX container, we all know that by default there is no direct access from the machine.

Just think about how many times you needed to debug your applications.And every single time you repeat the long commands in PowerShell , you wish it was a better alternative out there. Well, we felt that pain too. So, as software development is in our blood, we developed a tool to solve forever this pain.

If you want to upload an MSIX to the Microsoft Store, you might be overwhelmed by the process, or not know where to start. This article makes each step clear – you’ll have your app up and running in no time at all.

In our previous MSIX related blog articles, we’ve approached some of the MSIX particularities and different scenarios such as Digital Signing, MSIX Deployment via SCCM, MS-AppInstaller Web Protocol, and Context Menu.

Web protocols are not something new to the table. We have been using them for years, and they make our life a bit easier.

This article explores Microsoft's recommended solution for managing your Startup applications, when deployed as an MSIX package.

VLC media player (or in short VLC) is an open-source, cross-platform media player created by VideoLan. At the moment, its one of the most popular players on the market.Let’s see if we can convert it to the new MSIX technology by Microsoft and what challenges we face in doing so.

Notepad++ is the most popular free source code editor. Since MSIX is the future of packaging, let’s see how we can repackage Notepad++ to MSIX by using Advanced Installer.

Let’s assume that you have an application that installs files or registry in a user location. In this article we explain how you can install that information for all users by using MSI, APP-V or the new Microsoft installer technology, MSIX, a short cleanup process description, and a short comparison between them.

In January 2020, Windows 7 end of life support comes in place. This means that users won’t receive any updates from Microsoft, and companies have to pay extra for the next three years if they want them.

All MSIX packages must be digitally signed, no exception. In order to digitally sign your MSIX package, you can use a self-signed certificate. However, you need to ensure that same certificate used to sign the MSIX package is imported into the Computer's Trusted Root Certification Authorities on the target device where you plan to deploy your MSIX package. Otherwise, your MSIX will fail to install.

In our days, many apps offer you a context menu. A context menu is a pop-up menu that appears after a user interaction, for example, in Windows, when you perform a right-click. However, there are two types of context menus:

Before we begin, it is important we know that starting with SCCM version 1806, MSIX application is supported in System Center Configuration Manager. Integrating MSIX apps in previous versions, does not work. Also the current version of Windows 10 that supports MSIX is version 1809. It is announced that Microsoft will add support for MSIX also on other versions of Windows 10.

If we check the official Microsoft documentation about PackageName and appID, we can see that in theory, there aren’t so many differences between them.