If you are building a project from the VS Wix 'setup' template, it creates an MSI file, which is not an EXE file. So renaming the file to anything.EXE will produce a file that is not a PE file and is not compatible with being launched as a windows 'application'. The error message is telling you to put the OutputName back to what it was originally, .MSI. (You can install Orca from the Windows SDK and use it to look at a file which is a MSI file, but not an EXE file.)
Use the Wix 'setup' template to create your setup.MSI file. Then use the Wix 'bootstrapper' project template to create a Burn (Bundle) chain, bootstrapper.exe file. Add your MSI to the chain of the bootstrapper.exe (along with any other packages you may need to install). One way to approach this is to create a separate MSI for each 'application', without a UI in the MSI. The create a Burn bootstrapper.exe which provides the UI and chains all of the MSI packages. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/The-version-of-this-file-is-not-compatible-with-the-version-of-Windows-you-re-running-tp7592832p7592833.html Sent from the wix-devs mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
