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.
- The Dangers of ARPSYSTEMCOMPONENT
ARPSYSTEMCOMPONENTWindows Installer property can leave your Add/Remove Program entries behind.
- A Reason for ARPSYSTEMCOMPONENT
Reasons for setting
ARPSYSTEMCOMPONENTto 1 despite the dangers.
- Working with ARPSYSTEMCOMPONENT
How to work around the issues with ARP when defining
- Supporting our Lifecycle Policy with ARPSYSTEMCOMPONENT
How to support N and N-1 with the workaround for defining
- 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.