This site uses cookies for analytics, personalized content. By continuing to browse this site, you agree to this use. Learn More
Installation and containerization of the Visual Studio family of products
August 21, 2014Aug 21, 201408/21/14One frequently asked question is, “how do we register our program for a file extension when other versions (or programs) that handle it might also be installed?”
The overarching question is really about how to have non-shared resources both write to a shared resource.
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, when upgrading one product to update files shared with another product,
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.
December 21, 2009Dec 21, 200912/21/09Components are the basic unit of installation in a Windows Installer product. They are installed by one or more features, and can contain any number of resources including files, assemblies, registry values, and are recommended for custom resources as well. Examples of custom resources are web sites,
