Geek asks and answers

Application association

Sorry for the long post. My question is the best method to allow my users to assign file associations to my application. I turned it on to where I got it so far, but I'm not at all sure that I am looking at it correctly.

My application uses a specific extension (.ad2). It is launched by users using XP, Vista and Win7. I need to support them all. In Vista and Win 7, this requires administrator privileges. The location of my executable file may vary depending on where the user installs it. A good method, I think, would be to assign an association during installation. The problems here are that some of my users do not like automatic installers, and there is already a large installed base. So I got rid of this at the moment.

I want my users to control whether they are connected or not, so the process should be visible to them

The next time I thought that I needed to add code to the application, accessible through the menu. This works great because the application knows where it is installed. However, this requires running as an administrator (I understand that elevated privileges apply to the entire process). The user needs to elevate privileges before starting in order to bypass UAC.

Recently, I thought that he would switch to a new process from the main menu of the application, raise the permissions for this process and allow him to perform file association. The corrected executable will be in the same folder as my main application, so that it knows where things like the main executable and the icon are.

My preference is to lay out a new process - am I right?

thank

+3
source share
2 answers

, ScruffyDuck, UAC, , , Windows, , .

, , :

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> 
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel
          level="requireAdministrator"
          uiAccess="false"/>
        </requestedPrivileges>
       </security>
  </trustInfo>
</assembly>

: , , requestedExecutionLevel.

, UAC.

, , . .

+1

, . , . . :

var proc = new ProcessStartInfo {
                UseShellExecute = true,
                WorkingDirectory = Environment.CurrentDirectory,
                FileName = Path.Combine(Application.StartupPath, "ADEFileAssociator.exe"),
                Verb = "runas"
            };

try {
      Process.Start(proc);
    }
catch {
       MessageBox.Show("Failed to start File Associator","Process Error",MessageBoxButtons.OK,MessageBoxIcon.Error);
       return;
       }

. File Associator double , , Vista , . , . , , :

 var safeToRun = true;
 var os = Environment.OSVersion;
 if (os.Version.Major > 5) {//Got Vista or Win7
     if (!IsElevated) {
         var message = new StringBuilder();
         message.AppendLine("You are running Vista or Win7 and this program ");
         message.AppendLine("needs to run with Admin Privileges. When the ");
         message.AppendLine("program closes please right click on the executable");
         message.AppendLine("or icon and select 'Run As Administrator'.");
         message.AppendLine("");
         message.AppendLine("The Program will now close.");
         MessageBox.Show(message.ToString(), "Insufficient Privileges", MessageBoxButtons.OK, MessageBoxIcon.Error);
         safeToRun = false;
     }
 }

 if (safeToRun) {
     Application.EnableVisualStyles();
     Application.SetCompatibleTextRenderingDefault(false);
     Application.Run(new MainForm());
 }

IsElevated :

public static bool IsElevated {
   get {
         return new WindowsPrincipal
            (WindowsIdentity.GetCurrent()).IsInRole
            (WindowsBuiltInRole.Administrator);
       }
}

, .

, - . WinForm, .

, -. , ( )

0

More articles:


All Articles