Make sure all customs actions needing administration privileges are run
deferred with the NoImpersonate bit set.
You SHOULD NOT assume client side of your MSI is running with administration
privileges, it is a critical design mistake. Actions needing administration
privileges must be performed
Xin Liu (Person Consulting) wrote:
How to extract the registration information? I heard there are some
tools which can output a Wix include file containing the registration
information. But regit.exe doesn't provide that functionality.
Take a look at the tallow tool in WiX v2 or heat in
We have a .msi file built from Wix toolset which calls one of the VS SDK tool.
So if the .msi is ran in Vista, even if you are a member of Administrator
group, it will failed. However, if run it as Administrator (Right click
cmd.exe, choose Run as Administrator, then call the .msi from the
You need to make sure that your bootstrapper has one of the magical Vista
strings within it like setup or install. This will instantly elevate
the priveledges within Vista unless it has a corresponding Manifest file
telling it not to.
I get the impression that you're calling the MSI file
Xin Liu (Person Consulting) wrote:
We have a .msi file built from Wix toolset which calls one of the VS
SDK tool.
Please be more explicit. Which tool? As a custom action or a build-time
tool? Can you show a code fragment?
--
sig://boB
http://bobs.org
If you are an administrator and you install the MSI then it will elevate
when it goes to the InstallExecuteSequence (and work!) while the UI
sequence runs as standard user. If it's failing even though you are an
administrator then you are perhaps installing something from the UI
sequence. If this
How to extract the registration information? I heard there are some tools which
can output a Wix include file containing the registration information. But
regit.exe doesn't provide that functionality.
Thanks,
Xin
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 27, 2007 11:31
7 matches
Mail list logo
