This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can trysigning in orchanging directories.
Access to this page requires authorization. You can trychanging directories.
Use these pages to specify general options forMt.exe. These pages are found underProject >Properties >Configuration Properties >Manifest Tool.
Yes (/nologo) specifies that standard Microsoft copyright data will be concealed when the manifest tool is started. Use this option to suppress unwanted output in log files when you runmt.exe, either as part of a build process or from a build environment.
Yes (/verbose) specifies that more build information will be displayed during manifest generation.
Uses the/identity option to specify an identity string, which holds the attributes for the<assemblyIdentity> element. An identity string begins with the value for thename attribute, and is followed byattribute =value pairs. The attributes in an identity string are delimited by a comma.
Here's an example identity string:
Microsoft.Windows.Common-Controls, processorArchitecture=x86, version=6.0.0.0, type=win32, publicKeyToken=6595b64144ccf1df
Uses the/manifest option to specify the full paths of more manifest files that the manifest tool will process or merge. Full paths are delimited by a semicolon. (/manifest [manifest1] [manifest2] ...)
Uses the/inputresource option to specify the full path of a resource of typeRT_MANIFEST, to input into the manifest tool. The path can be followed by the specified resource ID. For example:
dll_with_manifest.dll;#1
Yes specifies that the project system will embed the application manifest file into the assembly.
No specifies that the project system will create the application manifest file as a stand-alone file.
Specifies the name of the output manifest file. This property is optional when only one manifest file is operated upon by the manifest tool. (/out:[file];#[resource ID])
Specifies the output resources file used to embed the manifest into the project output.
Uses the/makecdfs option to specify that the manifest tool will generate catalog definition files (.cdf files), which are used to make catalogs. (/makecdfs)
Generates a manifest from a managed assembly. (/managedassemblyname:[file])
Used with/managedassemblyname. Suppresses the generation of dependency elements in the final manifest. (/nodependency)
Used with/managedassemblyname./category causes the category tags to be generated. (/category)
Specifies whether the application is DPI-aware. By default, the setting isYes for MFC projects andNo otherwise because only MFC projects have built in DPI awareness. You can override the setting toYes if you add code to handle different DPI settings. Your application might appear fuzzy or small if it isn't DPI-aware, but you set a DPI-aware option.
Choices
For more information about isolated COM, seeIsolated applications andHow to: Build isolated applications to consume COM components.
Specifies the type library to use for regfree COM manifest support. (/tlb:[file])
Specifies the registrar script file to use for regfree COM manifest support. (/rgs:[file])
Specifies the file name of the component that is built from the .tlb or .rgs specified. (/dll:[file])
Specifies the file that contains values for replaceable strings in the RGS file. (/replacements:[file])
Computes the hash of files specified in thefile elements, and then updates the hash attribute with this value. (/hashupdate:[path])
Specifies the search path to use when updating the file hashes.
Allows you to specify more options.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?
Was this page helpful?
Want to try using Ask Learn to clarify or guide you through this topic?