Understanding how actions are sequenced when building or customizing Windows Installer (MSI) packages is essential.

Visual Studio is a complete development environment for writing, testing, and deploying applications across different platforms. Beyond coding, it also supports creating MSI installers directly within the IDE.

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.

The Windows Installer service is a standard in the industry when it comes to software packages, but it doesn’t mean it’s not prone to errors.

We’re excited to introduce a new, powerful addition to Advanced Installer: the Suite Installer feature.

When it comes to MSI technology, users might encounter a blocking point with the "Updating component registration" message during the installation process. This can be frustrating, but there are several solutions you can try to fix this issue. Let's explore them in this article.

When deploying MSI packages, IT professionals often encounter issues during installation, including stalls at the product information publishing phase. This crucial step updates system records so applications can be properly managed.

One common question packagers often ask themself is what type of installer to use when patching an application.

Encountering an ODBC connect timeout error during an MSI installation is uncommon but not unheard of.

For the past 10+ years, I have worked with various projects and types of organizations as an Application Packager. During that time, I have witnessed some "elementary" mistakes that could have been easily avoided by having a clear understanding of the end-to-end application packaging process.

As we head into 2025, the application packaging world feels familiar—like a well-worn tool that still gets the job done. While there’s always talk of “the next big thing,” much of what worked in 2024 will keep working. Let’s break down what to expect.

The role of a software packaging engineer is often misunderstood. Is it just a small part of a bigger process? Is it a “one-man show”? And do you really need one in your company?

In a previous blog article, we discussed what an EXE setup file is, the difference between EXE and MSI installers, and other general details related to Windows’ setup.exe.

Whether you're a seasoned developer or just getting started, Windows Sandbox is designed to make your application installer testing process smoother, safer, and more efficient.

Back in the days of Windows XP and the early stages of application repackaging for enterprise needs, quality assurance teams often needed to verify that the repackaged MSI package had the same structure as the original installation package.

This is not a new issue – it dates back to the transition days between Windows Vista, XP, and Windows 7.

Visual Studio is an integrated development environment (IDE) tool made by Microsoft to build code, and publish applications. It is mainly used to develop different types of software—from computer programs to web services.

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

PowerShell App Deployment Toolkit (PSADT) is the go-to solution for enterprises aiming to standardize their software deployment process.

Digital Signing should be a formality for professionals. It’s been almost 30 years since the first software was digitally signed but we still have many users who don’t know how or why they should use a code signing certificate. We need it to protect their intellectual property and enhance the cybersecurity of their end-users.