This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn More
February 20, 2011Feb 20, 201102/20/11Often I’m asked why installing a Windows Installer patch (MSP) takes as long or longer to install than the target product (MSI). While this isn’t always the case for every patch, it’s certainly possible for a number of reasons.
September 8, 2010Sep 8, 201009/8/10Shared components define shared resources. It might seem obvious, but it’s important to understand that whatever you do to a shared resource during the installation of one product affects those same resources for any other product. For example,
April 9, 2010Apr 9, 201004/9/10Major upgrades are Windows Installer products that can be installed like any other product with the added benefit of removing one ore more related products. For example, version 2 of a product can be installed on a clean machine, or on a machine with version 1 already installed and will remove version 1.
February 26, 2010Feb 26, 201002/26/10A while back I explained how Windows Installer sets the TARGETDIR property to the root of the fixed drive with the most free space available. The problem is that even an attached USB external drive can appear as a fixed drive,
February 15, 2010Feb 15, 201002/15/10When testing the serviceability of your product before you ship, it’s important to test any conditions you might have on the product, features, components, and actions.
Feature conditions can set the install level of a feature when the package is installed.
February 14, 2010Feb 14, 201002/14/10It’s always important to test your product before it ships. Servicing it later can prove very costly and very difficult. It’s no different with your installation packages. You need to test not only basic install and uninstall operations, but also test your servicing plan.
