The process of developing software should always include a solid mechanism for application upgrades.

When installing an application, it’s important to ensure all components required for the application to function properly are already installed on the target machine.

Windows Presentation Foundation (WPF) is a powerful User Interface (UI) framework for building desktop client apps. It's a part of .NET and offers a multitude of helpful features, such as media services, controls, data binding, and security.

Often throughout the repackaging process, it's frequent to come across files featuring straightforward paths such as: C:\Program Files.

In this article, we'll explore how to deploy an MSIX using Group Policies, covering Direct MSIX Deployment with Scheduled Tasks and the MSI Wrapper method.

.NET MAUI (Multi-platform App UI) is a cross platform framework designed for creating native mobile and desktop applications using C# and XAML. With the .NET MAUI platform, you can create applications that run on Android, iOS, MacOS, and Windows from a single code-base.

Batch scripting is still widely used within organizations all over the world, despite the popularity of PowerShell, which is a more powerful programming language. Almost every task or action can be executed by a sequence of commands typed on the Windows Command Prompt.

MSIX is a modern technology that has transformed the way we approach software installations and deployments, both for individual users and enterprises.

One of the greatest things about software packaging is the variety of choices available to you to achieve your objectives. However, having too many alternatives to choose from can make it challenging to pick the best one for your requirements.

Recently, I was assigned to monitor a third-party application to detect when a workstation is unlocked or a user logs in. Additionally, if the monitor goes off, the monitored app should be started.

Let's suppose you want to make changes to a build system so that it can perform multiple actions when building MSI or EXE packages.

In some cases, changing the packaging type of an application requires going back to the drawing board. Even though Advanced Installer's GUI lets you convert MSIX packages by importing them, changing the packaging type of an application can still be a bit tricky.

As an IT professional, you might have come across Windows Forms (WinForms) when building applications on Windows. WinForms is a free and open source GUI class library included in the .NET Framework that has been heavily used since its release in 2002.

In the tech industry, there's often a dilemma about which technology to use for patches. Specifically, when an ISV (Independent Software Vendor) creates an MSI for the first time and updates come up, they must choose between MSP and MSI options.

The GitHub Actions platform simplifies the automation of your software workflows. It allows you to build, test and deploy your code directly from GitHub, making it a super reliable CI/CD platform.

Electron is an open-source framework to develop desktop GUI applications using web technologies. It combines the Chromium rendering engine and the Node.js runtime.

In this article, we want to focus on desktop shortcut creation specifically for a Windows Forms application using the WiX Toolset.

In our previous articles, we discussed How to Set Automatic MSIX Downgrades with .appinstaller and the MS-AppInstaller Web Protocol, and now we will be discussing the technicalities of the .appinstaller.

One of the main challenges IT Pros face with application packages is the unattended installation. Unattended installations ensure that the same configuration is applied to all your active systems in the infrastructure, and no human error during installation can change that configuration.

Have you encountered an .appx file and wondered what it is and what it can be used for?