Using mt.exe to embed a manifest post build - erases my executable instead 1

[steve4king]

My version of InstallShield predates windows Vista and it's implementation of a embedded manifests/definable execution level.

I've found a bit of information suggesting that I could create a manifest and embed it using mt.exe.
However, whenever I attempt to add this manifest, it appears to wipe most of my installshield executable. (from 90mb down to 112kb)
No errors appear, only microsoft logo information.

my manifest file:

Executable: MyInstaller.exe 
Manifest:MyInstaller.exe.manifest
Sample application manifest file:
<?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="MyInstaller"
     type="win32"/> 
  <description>My program description</description> 
  <!-- Identify the application security requirements. -->
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel
          level="requireAdministrator"
          uiAccess="false"/>
        </requestedPrivileges>
       </security>
  </trustInfo>
</assembly>

my batch line:

mt.exe –manifest MyInstaller.exe.manifest –outputresource:MyInstaller.exe;#1

What am I doing wrong here?

 

[Olaf Doschke]

There is a simpler solution Riock Strahl found here:

http://www.west-wind.com/wconnect/weblog/ShowEntry.blog?id=890

In your project folder with yourapp.pjx, where you generate yourapp.exe, put your manifest int yourapp.exe.manifest and that manifest will be embedded into the exe by the foxpro BUILD. So you can distribute your exe without the separate manifest file.

Bye, Olaf.

 

[steve4king]

Thanks Olaf,
That's great information,(I'll definitely sticky that for later) but since it's the installer I want to restrict and not the program itself I'm not sure it will work for me.

Unless you're suggesting I wrap the installshield within a VFP project..?

 

[Olaf Doschke]

OK, I've overseen that. But Windows detects installers and requires Adminitrator privileges anyway, you don't need to embed a manifest for that into your setup.exe, If all else fails call it Setup.exe. You can try that even with a new, completely empty textfile you rename to Setup.exe. Windows will display it`s icon with the 4 color shieled sub image to denote requiring admin privileges.

Bye, Olaf.