API (ApplicationName.manifest)

Go Up to File Types Index

When you build a project for a Windows target platform, RAD Studio automatically includes an application manifest file. The application manifest file contains an XML list of dependencies for your application. For example, this is the manifest file that RAD Studio provides by default:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
 <dependency>
   <dependentAssembly>
     <assemblyIdentity
       type="win32"
       name="Microsoft.Windows.Common-Controls"
       version="6.0.0.0"
       publicKeyToken="6595b64144ccf1df"
       language="*"
       processorArchitecture="*"/>
   </dependentAssembly>
 </dependency>
 <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
   <security>
     <requestedPrivileges>
       <requestedExecutionLevel
         level="asInvoker"
         uiAccess="false"/>
       </requestedPrivileges>
   </security>
 </trustInfo>
</assembly>

The application manifest file provides information such as:

• Windows Common Controls support: Needed in order to use the newer version of native visual controls (also referred to as "XP Themes").
• Required application elevation level: Specifies whether the application needs to run with administrator privileges.
• DPI awareness: Specifies whether the application is designed to handle scaling based on different DPI values.

See Customizing the Windows Application Manifest File for more information and examples of custom application manifest files.

See Microsoft online documentation about the Application Manifests for more details about what the application manifest file may contain.

See Also

• Customizing the Windows Application Manifest File

• Windows Manifest in Application Options

• MSDN: Application Manifests

• Create and Embed an Application Manifest (UAC)