Bugs item #1616064, was opened at 2006-12-14 22:42 Message generated for change (Comment added) made by barnson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1616064&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: msbuild Group: None >Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: Kjell-Åke Andersson (spacelord72) Assigned to: pmarcu (pmarcu) Summary: Path to executables is hardcoded Initial Comment: When WiX is installed on Win x64 Votive will fail to execute when building a project with the error: Error 48 The specified task executable location "C:\Program Files\Windows Installer XML v3\bin\candle.exe" is invalid. C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.0\Wix.targets 109 6 MSMQStudioWiX It seems like the path to the executables are hardcoded in Votive. Please change the installer to put the path to the binaries into a regkey in HKLM and use it instead. ---------------------------------------------------------------------- >Comment By: Bob Arnson (barnson) Date: 2008-05-03 19:01 Message: Logged In: YES user_id=26581 Originator: NO This was fixed quite a while ago. The paths might exist in your .wixproj files, though, so you might have to edit them to remove it to let the defaults pick up. ---------------------------------------------------------------------- Comment By: Kjell-Åke Andersson (spacelord72) Date: 2007-04-22 22:28 Message: Logged In: YES user_id=1652392 Originator: YES Well, actually the problem is in the MSBuild tasks as it is them who are failing to find the executables. I submitted both a verbose installation log and screenshot from VS2005 displaying the error. I also tried to build the project with MSBuild from the VS2005 Command Prompt and it failed with the same error message. ---------------------------------------------------------------------- Comment By: Kjell-Åke Andersson (spacelord72) Date: 2007-04-22 22:24 Message: Logged In: YES user_id=1652392 Originator: YES File Added: wix3.png ---------------------------------------------------------------------- Comment By: Kjell-Åke Andersson (spacelord72) Date: 2007-04-22 22:24 Message: Logged In: YES user_id=1652392 Originator: YES File Added: wix3.log ---------------------------------------------------------------------- Comment By: Bob Arnson (barnson) Date: 2007-04-19 00:29 Message: Logged In: YES user_id=26581 Originator: NO Only Votive uses the registry value (not, say, the MSBuild tasks) so it's not a concern for build machines. (And the WiX tools are thin wrappers around wix.dll but unless we make the MSBuild tasks similar wrappers, we still need to be able to find them.) That said, I can't reproduce the problem with the latest weekly release. The correct path is written out: MSI (s) (38:EC) [17:22:43:031]: Executing op: RegAddValue(Name=ToolsDirectory,Value=C:\Program Files (x86)\Windows Installer XML v3\bin\,) WriteRegistryValues: Key: \SOFTWARE\Microsoft\VisualStudio\8.0\InstalledProducts\WiX, Name: ToolsDirectory, Value: C:\Program Files (x86)\Windows Installer XML v3\bin\ I'd suggest upgrading to the latest weekly. If it reproduces there, we'll need more details (like a verbose installation log). ---------------------------------------------------------------------- Comment By: Heath Stewart (heaths) Date: 2007-04-18 23:13 Message: Logged In: YES user_id=1335104 Originator: NO Using the registry directly or indirectly (say, through a component dir search) does not work well with build environments. I would suggest writing out a .config file or some sort of ini/config file that the installer (or some dev, admin, etc.) writes out, and that's how the WiX tasks find the executables to launch. Of course, another way would be to refactor the code for various tools like candle, light, etc., so that the EXE source is a thin wrapper around said functionality and the tasks reuse the refactored classes (say, in wix.dll). ---------------------------------------------------------------------- Comment By: Justin Rockwood (justinrockwood) Date: 2007-04-18 05:38 Message: Logged In: YES user_id=1054914 Originator: NO Bob, in Votive.wxs we're writing out a registry key that stores the value of the [BinDir]. What is the expected behavior here? ---------------------------------------------------------------------- Comment By: Kjell-Åke Andersson (spacelord72) Date: 2006-12-15 11:18 Message: Logged In: YES user_id=1652392 Originator: YES This would also be great for other tools that use WiX as well as it will be easier to find the executables. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1616064&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
