for new files that do not need to be registered to
null. (to allow for deletion in future patches)
Then apply the patch. Resulting in the null component id files not getting
installed.
Message: 6
Date: Tue, 14 Jan 2014 11:29:15 -0800
From: Phil Wilson
Subject: Re: [WiX-users] Deleting files
Non-versioned files are typically updated based on the file hash, If the
hash of the installed file is not the same as the hash of the incoming file
then the installed file will be updated. There's no need to do your own
patch mechanism with null component IDs.
http://msdn.microsoft.com/en-us/libr
olset.687559.n2.nabble.com/How-to-get-package-version-using-burn-API-tp7591717p7591752.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Message: 6
Date: Tue, 14 Jan 2014 11:29:15 -0800
From: Phil Wilson
Subject: Re: [WiX-users] Deleting files in a patch...
To: "Gener
More information on the issue we're trying to solve:
We need the ability to patch non versioned files /delete them if necessary,
etc. (in an MSP) We have found information indicating that removing the
ComponentID in the MSI will cause the Windows Installer to treat these
components as User D
It looks like you hijacked an existing discussion thread, so I'll start a
new one. ...
Yes, that's the way it works. That might not be the best way to remove
files if you decide you want them back later. An alternative is to make the
component transitive and use a property to make the actual file
5 matches
Mail list logo
