David L. Beckwith wrote: > > Yes, unfortunately that is what the custom action in the msi is doing. > > I could have sworn I tried the payloads under the BootstapperApplication > element, but I'll check again. > > > Rob Mensching-7 wrote: >> >> I'm a little confused. Are you saying the custom action is using the >> current working folder to find files? If so, that won't work out most of >> the time or rather it will work in very limited situations. >> If you want Payloads cached with the bootstrapper, you can add additional >> Payload elements under the BootstrapperApplication element. If you don't >> want them compressed mark them Compressed="no". >> > I remember why this did not work. The dlls need to be in the location of the bootstrapper, not the cache location. Argh!
I've given up this approach. The real solution here is a change in the MSI which I have no control. Another possibility is to use the bootstrapper that comes with this install which I suspect changes the working directory. I tried this a while ago but couldn't figure out how to create folders and designate which payload goes to what folder for burn. I also wasn't sure if an msi payload would be harvested like it is in an msiPackage. The other four chained packages work great! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-generate-tp6909632p6956991.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
