Don Benson wrote: > File/@Source="$(var.ClientInstall.TargetPath)" > > This worked great until I started to add the UI elements. I wanted to > localize the UI, so I added localization files (wxl) for the different > cultures we need. This broke the server compile. The localized clients are > generated in a separate subfolder for each culture, but the server build > breaks because it is looking for the client MSI in the folder that is the > parent to the culture folder. > > Should this be working? >
It'd be great if there were a way but there's nothing that ties together the multiple outputs of a localized .wixproj into multiple inputs for another .wixproj. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
