After completing what I thought were all the Vista updates necessary for our
installer, an issue came up when installing per user. One of our COM
component's (packaged as on ocx) registry entries are inaccessible in some
scenarios.
I read this entry:
http://blogs.msdn.com/cjacks/archive/2007/02/21/per-user-com-registrations-and-elevated-processes-with-uac-on-windows-vista.aspx
and it looks like if the user is a local admin and they turn off UAC, then
the per user registry entries are not available.
Because we can not enforce whether or not a user is running as an
administrator with the UAC disabled, is the only fix to register per machine
on Vista?
Ideally, because our product is only supported on XP and newer, I'd like to
use the side-by-side mechanism and not register COM at all, but I have been
unable to create a manifest that works. Any pointers on this would be
greatly appreciated.
Also, I am having a debate with the project leader about the ALLUSERS
property. He wants me to set it to 1 in the installer and remove the option
from the UI. He figures that this issue will go away, but I am reluctant as
I would like to fix it the right way. Am I wrong to resist his suggestion
or should I give in and deal with the issues (if any) that arise from making
our installer a per-machine installer?
John
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
