ARPSYSTEMCOMPONENT and Sequencing

ARPSYSTEMCOMPONENT and Sequencing

  • Comments 3

Sequencing Windows Installer patches is typically straight forward but when the original product install or a previous, non-superseded patch defines ARPSYSTEMCOMPONENT as 1 in the Property table a custom supersedence plan is necessary to support writing Add/Remove Program registry keys correctly with patch supersedence and sequencing in mind.

  1. The Dangers of ARPSYSTEMCOMPONENT
    Using the ARPSYSTEMCOMPONENT Windows Installer property can leave your Add/Remove Program entries behind.
  2. A Reason for ARPSYSTEMCOMPONENT
    Reasons for setting ARPSYSTEMCOMPONENT to 1 despite the dangers.
  3. Working with ARPSYSTEMCOMPONENT
    How to work around the issues with ARP when defining ARPSYSTEMCOMPONENT=1.
  4. Supporting our Lifecycle Policy with ARPSYSTEMCOMPONENT
    How to support N and N-1 with the workaround for defining ARPSYSTEMCOMPONENT=1.
  5. A Better Way of Working with ARPSYSTEMCOMPONENT
    How to support custom supersedence when you have to manage patch-specific registry keys manually without using a lot of custom code.
Leave a Comment
  • Please add 5 and 6 and type the answer here:
  • Post
  • By default, an MSI-based setup will appear in Add/Remove Programs when it is installed on a system. ...
  • How to create a patch-specific property to help identify whether patches were applied to an administrative image being installed.
  • In response to a previous post where I mentioned that work was being done on Visual Studio 2005 SP1,...
Page 1 of 1 (3 items)