Hi all, Been playing around with Burn (and searching the archives) and I'm not clear on something.
I'm using the standard WiX bootstrapper to chain some WiX MSIs that are in the same solution. I don't want to embed the MSIs, need to keep them separate. I can of course hardcode the SourceFile path to point to the WiX MSI's output directory. This works fine when I'm building the bootstrapper and all setups manually within Visual Studio. The problem is I don't actually want the MSIs deployed in that folder structure for a release (bin\Debug or bin\Release). Is there a clean way to handle this? The best I can do right now is adding some post/prebuilds to the bootstrapper project and copying each chained MSI to a specific place on each build and referencing that relative path from the bootstrapper. Thanks, Ben NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
