Bugs item #1670270, was opened at 2007-02-27 19:23 Message generated for change (Comment added) made by barnson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1670270&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: documentation Group: v3.0 Status: Closed Resolution: Rejected Priority: 5 Private: No Submitted By: elsapo (elsapo) Assigned to: Bob Arnson (barnson) Summary: tutorial shows candle run at comandline, but doesn't work Initial Comment: Summary: Tutorial should show the use of a working commandline, not one that will fail, eg, show this: "%ProgramFiles%\Windows Installer XML v3\bin\candle.exe" mywxs.wxs ------------- I just installed wix3. The shipped documentation includes Getting Started, which shows this: C:\test> candle product.wxs AFAICT, the wix3 installer doesn't create a "c:\test" directory, and doesn't put candle into the path, so this doesn't work. I considered fixing it myself by adding the bin directory for candle to my PATH, but then I reconsidered -- the installer chose not to put it into my PATH, so I probably shouldn't either, until I know how they made that choice. Actually, first it is tough to find the directory, because it isn't called wix, and the installed shortcuts on the program menu don't seem to include the path. After I finally figured out where it is (ProgramFilesDir\Windows Installer XML v3) I've been invoking it with fully qualified name, eg, "%ProgramFiles%\Windows Installer XML v3\bin\candle.exe" mywxs.wxs I didn't think that would work -- I thought it would be missing dlls -- but it turns out to work. It would be great if this were added to the documentation where they show candle being run, so that the user can actually use the command in the tutorial successfully. ---------------------------------------------------------------------- >Comment By: Bob Arnson (barnson) Date: 2007-10-23 04:28 Message: Logged In: YES user_id=26581 Originator: NO On x64, the ProgramFiles environment variable is either "Program Files" or "Program Files (x86)" depending on the bitness of the cmd.exe used (and system language). There's no environment variable that works for both x86 and x64. WiX, being a 32-bit package, installs to "Program Files (x86)" by default on an x64 box. And it can be changed to any arbitrary path by the user, so no environment variable would work in that case. ---------------------------------------------------------------------- Comment By: elsapo (elsapo) Date: 2007-10-23 03:26 Message: Logged In: YES user_id=1195173 Originator: YES Oh, I didn't notice you closed this, so I guess that means you've no further interest in it, which is fine with me. But if there is a bug with this environment variable, it will affect many scripts all over the world -- could you tell me about it, so I can be wary of it? ---------------------------------------------------------------------- Comment By: elsapo (elsapo) Date: 2007-10-23 03:24 Message: Logged In: YES user_id=1195173 Originator: YES > The user can change the installation path That was why I use the environment variable "%ProgramFiles%" instead of a hardcoded path, yes? Are you saying that there is a bug with this environment variable on 64-bit windows? I've developed scripts that work on both 32-bit and 64-bit, but the main problem I've hit is the problem that there are two different cscript.exe, one for 32-bit and one for 64-bit, and two different registry areas, so it gets tedious for the script to work for either (sub)world. ---------------------------------------------------------------------- Comment By: Bob Arnson (barnson) Date: 2007-10-22 18:00 Message: Logged In: YES user_id=26581 Originator: NO The user can change the installation path and on x64 OSes, the default path is "Program Files (x86)," so it's not possible to give an "always-works" path. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1670270&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
