I've got an MSI (that's somewhat polished, thanks to this list!) using the
AssemblyApplication parameter on the File tag for "autohealing" and dependency
tracking. An example is shown below:
<Component Id="pantheruicommondll" Guid="C74CD124-E5E4-0C6C-21DB-BE9D77C96269">
<File KeyPath="yes" Id="panther.ui.common.dll"
Source="\release\panther.ui.common.dll" Assembly=".net"
AssemblyApplication="SoftekWeb.dll">
<netfx:NativeImage Id="pantheruicommondllngen" Platform="all" Priority="1"
/>
</File>
</Component>
Installing on Vista requires administrative privileges, because we write to a
subfolder inside of ProgramFilesFolder. There is a condition testing for this.
<Condition Message="This installation requires administrative
privileges.">Privileged</Condition>
However, after the installation is completed (for ALLUSERS), if an
administrator forcibly removes a file that's required, the MSI will try to
auto-heal itself. This works wonderfully, if the current user is also an
administrator. How can I make Vista require privilege elevation on normal
users to have the MSI repair itself, rather than failing?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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
