Digital signing ensures software integrity and authenticity. It’s a fundamental practice in digital safety practices that establishes trust between software developers and users.

Creating an installation package is a crucial step in software deployment, and choosing the right packaging tool can significantly impact the process. Each tool has its advantages and disadvantages. Your choice depends on factors such as project complexity, ease of use, or the need for advanced features.

After creating a software application, the next step is to create an MSI installer for it.

The MSI format is a widely recognized standard in the software industry for distributing software packages to Windows-based devices. MSI packages offer numerous advantages over alternative software installation methods, including enhanced reliability and improved performance.

When it comes to installing or uninstalling an application package, the level of user interaction can vary based on your specific needs. In cases where you prefer to minimize user involvement, a convenient solution is to opt for a silent install or uninstall. With a silent installation, users are spared the hassle of navigating through an installation wizard and repeatedly clicking the "Next" button.

As part of the software packaging industry, you're most likely familiar with Windows Installer XML, or WiX. The WiX Toolset is widely used to build Windows Installer packages.

During the installation process, user input dialogs play a crucial role by prompting users to provide necessary input. This feature is widely utilized in setup packages as it allows users to provide feedback, and it ensures proper installation and configuration of the software. Additionally, it allows you to store valuable information on the local machine for future use.

When creating an installer, it is crucial to prioritize the setting of the installation directory. This directory, often referred to as the "install path," represents the specific location on the user's computer where the application will be installed.

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.

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

Although it is not required, almost every WiX UI configuration has a License Agreement Dialog. In this article, we will go through how to use WiX Toolset to build an installer without a license page.

Do you want to transfer CustomActionData to a CustomAction in WiX? We'll show you how in this article.

Deploying major upgrades for an MSI package created with WiX Toolset is simple. However, there are a few boxes you need to check to make sure you're doing it properly. We'll share them with you in this article!

When uninstalling an application, Windows Installer removes by default only the files that were created during the installation process. But, how about the files that are created after the installation?

When you create an installer using the WiX Toolset, there are instances where you may want to set a custom action to run under specific conditions, such as uninstalling an application, installing an application, or running a custom script.

When you define shortcuts in WiX Toolset, their default installation is non-advertised (Standard Shortcuts).

In some instances, when uninstalling an MSI, you may notice that some files and folders stay in the system and are not removed.

One of the most asked questions in the industry is related to CAB files and what embedding options these have within the WiX Toolset.