Re: How can I integrate within the PDK perlapp the manifest assembly workaround for Vista UAC?

[syphilis]

If you can't get a satisfactory solution here, consider posting to ActiveState's PDK mailing list.

Cheers,
Rob
Afterthought: Can you achieve success by creating a separate file ? ie, assuming your executable is named 'script.exe', create another file (in the same folder) called 'script.exe.manifest' that looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.
+0">
  <assemblyIdentity version="1.0.0.0"
     processorArchitecture="X86"
     name="script.exe"
     type="win32"/>

  <!-- Identify the application security requirements. -->
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel
          level="asInvoker"
          uiAccess="false"/>
        </requestedPrivileges>
       </security>
  </trustInfo>
</assembly>

That worked for me in relation to a 'patch.exe' that I copied across from a Windows 2000 box. (The excutable wouldn't run until I created 'patch.exe.manifest')

[ddn123456]

Hi Rob, Just tried out your suggestion. Unfortunately as of Win2003 and now also on Vista, if an internal manifest exists this is executed and any external manifest is ignored. Once I have "manifested" all the exe's from the pdk & perl. (I'm especially thinking of the perl.exe). I'll run a last test. If this doesn't do the trick. I'll post it with a link to this page on ActiveState Thanks anyway! With kind regards. DDN