Roel Harbers wrote:
> Oh, and where did the "install for me/all users" option go?
On further reading of docs and a bit of experimentation, it seems like
having this choice, and remembering the previous choice, is a waste of
First of all, the choice only affects which account's start menu the
_shortcuts_ to the program get installed to - AllUsers or <CurrentUser>.
The applications and shell extension are available to everyone (unless
it's install location is somewhere that other users explicitly don't
have access to).
Secondly, if we want to remember which choice got picked last time, we
have to use two registry keys; one to record the username of the
installing user from last time, the other to record the radio button
they picked. Then if the user is the same this time, we use the choice
as stored in the registry. If the user doesn't match, we have to store
_this_ username and choice, too. We could conceivably end up storing
many usernames and choices in the registry, which seems nasty (to me).
Thirdly, there appears to be a "sensible default" that can be applied
without asking the user to click on something; to wit - if the user is
an admin, install to the AllUsers account's start menu; if the user is
not an admin, install to their own account's start menu.
Fourthly, it's an unbelievable pain in the ass to modify the dialogs
using just text. WiXTool is a great help for the previewing, but still
gets a few things wrong; has no editing-grid, snap-to function,
multiple-selection-move, undo/redo, and the saved output messes with the
order of the XML source of the controls in _every_ dialog in the file
(not just the one being edited) (which would make diffing and merging a
nightmare). It's taken an evening just to rearrange the controls on one
form to make room for a pair of poxy radiobuttons and a label. Whinge.
So, if there are no objections, I'm going to opt for the sensible
default and eliminate the headache entirely. Tomorrow.
Note that it will still be possible, as far as I understand things, to
perform a command-line install and specify the ALLUSERS property there,
which should override the sensible default - see
http://www.appdeploy.com/faq/detail.asp?id=69 . One might want to do
this if one is an admin, but wants the shortcuts to only be in one's own
user profile. In our case, a shell extension, I would contend that
that's pretty much the definition of an edge case, though...
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Aug 13 00:47:04 2005