Re: [WiX-users] HEAT5150: Could not harvest data

able to help you out. Thanks, Brian Rogers "Intelligence removes complexity." - Me http://blogs.msdn.com/icumove <-- NEW On Fri, Jan 22, 2010 at 4:30 PM, jwalker wrote: > Thanks for your response... Good questions all... I'm trying to figure out > just what the differ

Re: [WiX-users] HEAT5150: Could not harvest data

but not by much. At least it is obvious. Is your build machine 32-bit or 64-bit? Are there any obvious differences between the files that heat processes OK and the ones that it errors on? Are the files .net or native code? -Original Message- From: jwalker [mailto:improvi...@yahoo.com]

[WiX-users] HEAT5150: Could not harvest data

Hi, I get this error from heat.exe for certain ocx and ax files. The files register correctly using regsvr32 from the command line. Is there any resolution to this problem or some workaround for auto-generating the registry entries? Or am I going to have to call regsvr32 from a CA (yuk)? Thanks,

[WiX-users] Error 1648 Installing Patch

Hi, I have a patch built using the WiX-only approach. I can view it in Orca with the original MSI, and everything looks good. But when I go to apply the patch, the installer displays the message "No valid sequence could be found for the set of patches". The values are all correct in the MsiPathS

Re: [WiX-users] Extra Files in Patch

you would need to change your build process to create admin images and then run torch on them. -----Original Message- From: JWalker [mailto:improvi...@yahoo.com] Sent: Wednesday, September 02, 2009 6:54 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Extra File

[WiX-users] Extra Files in Patch

Hi, I am using the WiX-only approach described in the wix3 chm to create patch packages. In some cases lots of extra files (files that have not changed from the baseline version) are being included in the patch, maybe hundreds. They are not referenced in the patch.wxs file, and I have no idea ho

Re: [WiX-users] Environmet Variable Propagation

Yeah, removing the app's dependency on the environment variable would be the way to go. Unfortunately, that's not an option in this case. The weird thing is if you go look at the environment variables in the control panel and click OK, it does get propagated to subsequent command prompts. So the