It's not exactly clear what you're doing, but the way this works (to state the obvious maybe) is that you build the MSI file on your dev machine and then take that MSI file to other machines and run it to install the product. If you have a problem installing the MSI file on another machine, then describe it exactly because describing it as "related to file not found" isn't useful. MSI install failures give error text and an error number, they would help, and running with a msiexec command line to produce a verbose log will also tell you what's going on. --------------- Phil Wilson
On Sun, May 11, 2014 at 10:06 PM, <b.ras...@leonit.nl> wrote: > Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar > basti...@careercontrol.nl. > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
