Re: [WiX-users] Problems with deactivating a component while package removal

Guten Tag Blair, am Dienstag, 13. Oktober 2009 um 05:57 schrieben Sie: > And changed it to this: > File="[SignWrapper_RootDir]signwrapper.xml" Action="setValue" Value="0" > ElementPath="//signwrapper/BEFDE7B3-54DB-419e-BB46-5FA8CE997AD5/spezial/disa > blePdfInline" Sequence="1" /> >

Re: [WiX-users] Problems with deactivating a component while package removal

Re: [WiX-users] Problems with deactivating a component while package removal Guten Tag Blair, am Samstag, 10. Oktober 2009 um 23:58 schrieben Sie: > What are the criteria used to determine which of the four components > operates on the file? The components are bound to a feature for each c

Re: [WiX-users] Problems with deactivating a component while package removal

Guten Tag Blair, am Samstag, 10. Oktober 2009 um 23:58 schrieben Sie: > What are the criteria used to determine which of the four components > operates on the file? The components are bound to a feature for each component which is designed to change exactly one config value. I have a feature and

Re: [WiX-users] Problems with deactivating a component while package removal

I don't quite understand what you are attempting to do. You have some component somewhere that installs a file ([SignWrapper_RootDir]signwrapper.xml) that four other components modify upon installation and "revert" upon removal. So far so good. What are the criteria used to determine which of the