Manifest file is generally put into the resource section of the application. Typical manifest file with administrator privilege and with no "uiAccess" appears like this.
 
  <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
   <assemblyIdentity type="win32" processorArchitecture="*" version="1.0.0.0"  
   name="MyApplication.exe"></assemblyIdentity>
   <description>Vista Application</description>
   <dependency>
    <dependentAssembly>
     <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls"
     version="6.0.0.0" language="*" processorArchitecture="*"    
     publicKeyToken="6595b64144ccf1df"></assemblyIdentity>
    </dependentAssembly>
   </dependency>
   <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
    <security>
     <requestedPrivileges>
       <requestedExecutionLevel level="requireAdministrator"  
       uiAccess="FALSE"></requestedExecutionLevel>
     </requestedPrivileges>
    </security>
   </trustInfo>
  </assembly>
 

VistaUACMakerConsole [-d <description>] [-p <priv level>] [-ui] {exe_path}

Options:
   -d  Description of the project ( Default : My project )
   -p  Privilege level required. possible values : admin, invoker, highest
       admin = administrator
       invoker = same as parent process
       highest = Highest possible level for the user
   -ui Specify if the executable interacts with higher windows.
       (Default action is not to set this flag)

Example:
    VistaUACMakerConsole -d "Vista project" -p admin "c:\project.exe"