manifest creation using mt.exe unrecognized element requestedPrivi

[Guest]

I want to "mark" an exe with a requestedPrivilege level. I have created a
manifest <below>. My target machine is, of course, Vista. My development
machine is XP Pro. When I run my built from Visual Studio 2005 I get a
manifest warning.

I am wondering "where" the DTF file is or is it another mechanism that
doesn't have the entry for where does it actually get
urn:schemas-microsoft-com:asm.v2?
Any ideas how this works?

Here is the manifest
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v2" manifestVersion="1.0">

<assemblyIdentity

version="1.0.0.0"

processorArchitecture="X86"

name="KofaxImageProducts.AscentCapture.QualityControl"

type="win32"

/>

<description>Ascent Capture - Quality Control</description>

<dependency>

<dependentAssembly>

<assemblyIdentity

type="win32"

name="Microsoft.Windows.Common-Controls"

version="6.0.0.0"

processorArchitecture="X86"

publicKeyToken="6595b64144ccf1df"

language="*"

/>

</dependentAssembly>

</dependency>

<ms_asmv2:trustInfo xmlns:ms_asmv2="urn:schemas-microsoft-com:asm.v2">
<ms_asmv2:security>
<ms_asmv2:requestedPrivileges>
<ms_asmv2:requestedExecutionLevel level="asInvoker">
</ms_asmv2:requestedExecutionLevel>
</ms_asmv2:requestedPrivileges>
</ms_asmv2:security>
</ms_asmv2:trustInfo>
</assembly>

 

[Jimmy Brush]

Hello,

Try changing this line:

<ms_asmv2:trustInfo xmlns:ms_asmv2="urn:schemas-microsoft-com:asm.v2">

To:

<ms_asmv2:trustInfo xmlns:ms_asmv2="urn:schemas-microsoft-com:asm.v3">

 

[Guest]

Thanks, I will give it a try. It turns out that I can solve the problem by
using the version of mt.exe that comes with the Vista SDK which is diffent
from the Visual Studio program MARKED WITH THE SAME EXACT VERSION.
5.2.3790.2075

see
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=258108

It also turns out that the warning is "harmless" in that the HTML does get
embedded into the manifest and recognized by Vista even with the warning.

THanks,
Chas