I've just modified my install build to call light.exe (via the MSBuild task) with -xo and -bf and then do a second pass with the .wixout (also via the Light MSBuild task) so I can bind the install binaries into the .wixpdb. I want to generate patches without using admin installs, but since I want the install and patch builds fully automated in our build, I can't satisfy the requirement of having the old and new binaries in the exact same path so I can use the standard .wixpdb with torch. I have the .wixout to .msi/.wixpdb method working, but I ran into a problem with the Wix UI stuff when doing it this way.
My install defines paths for the banner, icons, etc using WixVariable and the appropriate IDs. These work fine if I build the install project normally. However, when I use two passes, all of the images go back to the Wix defaults as though I'd never changed them. I opened the .wixout file and looked at the Wix variable values, which do have the paths to the files I would have expected. Those binaries do not appear to be making it into the .wixout, though. The same thing happens even when I use light.exe from the command line, so I know it has nothing to do with my MSBuild integration. I tried passing the WixUI extension to light.exe on the second pass, but that made no different. I tried explicitly setting the Wix variable values on the second call to light, but it complained about a duplicate definition of the variable. I managed to work around this problem by copying the contents of Common.wxs from the WixUIExtension wixlib into my project, changing the Binary items to my own source files, and referencing that fragment instead of WixUI_Common. I can live with the workaround if I have to, but if there's a way to make this work with the normal WixVariable declarations, I'd love to know. Thank you, Jeff ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
