There is a bug open on this: http://wixtoolset.org/issues/3640/
You can usually work around this by using subfolders, like setting the Exepackage Name="Exepackage1\Setup.exe". On Thu, May 15, 2014 at 9:47 AM, Valentine Vinogradov <wallenw...@gmail.com>wrote: > Hello! Are there any possibilities to prevent taking local files with the > same name laying in download folder for the package expected to be > downloaded? > For example, if I have Exepackage Name="Setup.exe" with download url and > remotepayload, it tries to take file setup.exe in the execute folder and > check it, and, of course, fails. > > ------------------------------------------------------------------------------ > "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
