VS2005, introducing app.manifest in 2008,2010 (that is, C # programs run with Administrator privileges under Win7)

Open VS2005, VS2008, VS2010 project, see if there is a app.manifest file under the Properties folder in the project folder; if not, create it as follows: Right-click the project Select "Properties" from the menu and click on "Security" of the project properties. tab, check "Enable ClickOnce Security Settings" On the Security tab and select "This is a fully trusted application" to save the project, where the App.manifest file has been automatically generated under properties.

Change the default app.manifest file to

[HTML]View PlainCopy

2. <? XML version= "1.0" encoding="Utf-8"?>
4. <asmv1:assembly manifestversion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1 "
8. xmlns:asmv1= "urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="Urn:schemas-microsoft-com:asm.v2 "
12. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
14. <assemblyidentity version="1.0.0.0" name="Myapplication.app"/>
16. <trustinfo xmlns="Urn:schemas-microsoft-com:asm.v2">
18. <security>
20. <requestedprivileges xmlns="Urn:schemas-microsoft-com:asm.v3">
22. <!--UAC Manifest Options
24. If you want to change the Windows User account Control level replace the
26. requestedExecutionLevel node with one of the following.
28. <requestedexecutionlevel level="AsInvoker" uiaccess="false" />
30. <requestedexecutionlevel level="requireadministrator" uiaccess="false" />
32. <requestedexecutionlevel level="highestavailable" uiaccess="false" />
34. If you want to utilize File and Registry virtualization for backward
36. Compatibility then delete the requestedExecutionLevel node.
38. -->
40. <requestedexecutionlevel level="requireadministrator" uiaccess="false" />
42. </requestedprivileges>
44. </Security>
46. </trustinfo>
48. </asmv1:assembly>

After the configuration file is modified, we run the application, we will first pop up such a prompt box, click Yes, the program can continue to run.

By the way, there is also a way to find out if the program is running as Administrator right at this point:

[CSharp]View PlainCopy

1. Public static bool Isadministrator ()
2. {
3. WindowsIdentity identity = WindowsIdentity.GetCurrent ();
4. WindowsPrincipal principal = new WindowsPrincipal (identity);
5. return principal.  IsInRole (Windowsbuiltinrole.administrator);
6. }

The UAC execution permission level referenced in the XML file represents the following meanings, respectively:

AsInvoker: The application is running with the current permissions.

Highestavailable: This is run with the highest privileges available to the current user.

Requireadministrator: This is only run with system administrator privileges.

By default, it is AsInvoker.

Both the highestavailable and Requireadministrator options can prompt the user for system administrator privileges. So what's the difference between these two options?

The difference is that if we are not logged in as an administrator account, then if the application is set to Requireadministrator, then the application will fail to run directly and cannot start. If set to Highestavailable, the application can run successfully, but runs with the permissions of the current account instead of system administrator privileges. If we want the program to run when a non-admin account is logged in (in which case some functionality should be limited), we recommend that you configure it with highestavailable.

VS2005, introducing app.manifest in 2008,2010 (that is, C # programs run with Administrator privileges under Win7)