SciTE edit as admin by default

[Sn3akyP3t3]

I previously ran SciTE and Autoit from a Windows XP machine and therefore didn't have any UAC or privileges issues to deal with. Now I'm running Win7 64 bit and noticed that when opening a .au3 file I don't get any prompt choice to run as admin. It simply opens the file I requested. When I hit F5 or click on "Go" to run the application SciTE is unable to hook into the app and get Console output when run like this.

I can, however, go through the trouble of opening SciTE independently as administrator before opening the source code .au3 files and when I hit f5 or "Go" like this I am again able to get ConsoleWrite output as well as get runtime errors.

My question: Is it possible to modify the SciTE editor so that it prompts to run as administrator when attempting to open a .au3 file rather than right clicking on SciTE and manually selecting to run as administrator and then opening the .au3 file? I'm trying to achieve a shortcut and save time while removing one more annoyance that is UAC Win7 powered.

Many thanks!

[Sn3akyP3t3]

I found a method that works, but it isn't the method I was looking for. I was looking for the SciTE equivalent to AutoIt's #RequireAdmin. If someone has the answer to this still I would appreciate it.

Meanwhile, what I discovered is allow the OS to request privilege elevation at runtime. Right clicked on SciTE.exe in the program files dir -> Properties -> Compatibility Tab -> check "run......as an admin..."

This same idea can be applied to a shortcut under a different submenu, but I did it to the .exe since I would rather open the .au3 file directly to get the prompt and be done with the whole process quickly!

[BrewManNH]

That's probably the best way of having SciTE run under admin credentials. I don't believe there's any command in the SciTE configs that would tell it to ask for Admin privileges before running.

[Sn3akyP3t3]

Too bad. It works this way, however, regardless if SciTE is running the UAC elevation prompt presents its annoying self for every instance a new .au3 is opened and then gets applied as a new tab on the running SciTE editor. Regardless, it could always be worse I suppose. At least I have my sight and my hard drive hasn't failed this year! .)

[Jos]

I currently have no option to test this, but maybe creating your own manifest by creating file scite.exe.manifest in the scite directory containing the below will force this?

<?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.v3">
    <security>
        <requestedPrivileges>
            <requestedExecutionLevel level="requireAdministrator" uiAccess="false"/>
        </requestedPrivileges>
    </security>
</trustInfo>
</assembly>

Just a thought

[Jos]

mmm... that clearly didn't work, but it does work when you replace the current Manifest inside of SciTE.exe with the below info:

expandcollapse popup

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
                 manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
<assemblyIdentity
    version="1.0.0.0"
    processorArchitecture="*"
    name="Scintilla.SciTE.SciTE"
    type="win32"
/>
<description>SciTE</description>
<asmv3:application>
    <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
        <dpiAware>true</dpiAware>
    </asmv3:windowsSettings>
</asmv3:application>
<dependency>
    <dependentAssembly>
        <assemblyIdentity
            type="win32"
            name="Microsoft.Windows.Common-Controls"
            version="6.0.0.0"
            processorArchitecture="*"
            publicKeyToken="6595b64144ccf1df"
            language="*"
        />
    </dependentAssembly>
</dependency>
<!-- Identify the application security requirements. -->
<!-- level can be "asInvoker", "highestAvailable", or "requireAdministrator" -->
   <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
      <security>
      <requestedPrivileges>
        <requestedExecutionLevel
          level="requireAdministrator"
          uiAccess="false"/>
      </requestedPrivileges>
    </security>
   </trustInfo>
</assembly>

You can do this with reshacker or CFF Explorer, which I use mostly.

Jos

[Zedna]

Another elegant solution is to DISABLE UAC completely, I use it this way on my Win7 64bit.