Re: [WiX-users] Pyro not creating deltas despite using the -delta flag

Windows Installer uses an API that is now called PatchAPI for the actual "delta" compression. That API (along with its more modern replacement, which Windows Installer does not natively support) is documented on this page: http://msdn.microsoft.com/library/bb417345.aspx. One aspect of the algorithm

Re: [WiX-users] upgrading custom actions to be data driven

Hi Chris: Several things, There are multiple language directories for multiple versions of the product I'm installing to. Also,m binary files have to be created whilst installing and hence added to the RemoveFiles table. Hope this explains things. Cheers Sean. -Original Message- From: Ch

Re: [WiX-users] upgrading custom actions to be data driven

Before I begin describing how to refactor hard wired custom actions to data driven custom actions,  I have to ask:   Can your problem be solved using Windows Installer's built-in Condition table?   What is unique about your story that requires a custom action in the first place?   Christopher Pa

Re: [WiX-users] Setting a property to a filename already in my msi

(since CustomActionData is the alias for the property named the same as the deferred custom action itself). See http://msdn.microsoft.com/library/aa368609.aspx for details on when this is will work and what you will get: If a substring of the form [#filekey] is found, it is replaced by the full

[WiX-users] upgrading custom actions to be data driven

Hi: I'm currently in the process of upgrading my custom actions to be data driven. In the current implementation of the msi I'm using properties to enable/disable feature visibility. Is there a way to do this from a table given that what was about 30 properties are now going to be entries in a cu

Re: [WiX-users] Patch Creation Issues

Some notes on how that patch creation process works: 1. Torch doesn't look at the files themselves, only at the metadata for them already captured in Windows Installer tables. In part because of this (but mostly because some other data that isn't likely to change is also needed when building the M

Re: [WiX-users] Collateral learning Opportunity

>From that same project, a built copy of the extension appears to be in the tree (see http://code.google.com/p/ossbuild/source/browse/trunk/Shared/WiX/OSSBuildExt ensions.dll) You'll need to use the link at the lower-right side called "View raw file". If you download the dll via the web browser y

[WiX-users] Setting a property to a filename already in my msi

Hi: How would I go about setting the CustomActionData property to a filename already in my msi, is using the file id sufficient? Also, would this filename include the full path? Any help appreciated. Regards Sean. -- Prote

Re: [WiX-users] Wix upgrade process does not consider 4th part of the version string

Hi, read this thread. Maybe this is what you need: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setup-upgrade-needs-to-care-for-4th-part-of-version-number-td3250189.html Dirk On Fri, Jan 14, 2011 at 23:55, Wilson, Phil wrote: > That's a Windows Installer limitation on upgrad