source: trunk/eraser6/Installer/Bootstrapper/Bootstrapper.manifest @ 1923

Revision 1923, 626 bytes checked in by lowjoel, 4 years ago (diff)

I'm not going to leave it to chance -- without including the requestedExecutionLevel element the bootstrapper may still be run as administrator if the OS heuristically determines it is a setup file. Explicitly say it isn't until the payload is integrated.

Line 
1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
2<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
3    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
4        <security>
5            <requestedPrivileges>
6                <requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
7            </requestedPrivileges>
8        </security>
9    </trustInfo>
10    <dependency>
11        <dependentAssembly>
12            <assemblyIdentity type="Win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*" />
13        </dependentAssembly>
14    </dependency>
15</assembly>
Note: See TracBrowser for help on using the repository browser.