Manifest Generation at the Command Line
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
The latest version of this topic can be found at Manifest Generation at the Command Line.
When building C/C++ applications from the command line using nmake or similar tools, the manifest is generated after the linker has processed all object files and built the final binary. The linker collects assembly information stored in the object files and combines this information into a final manifest file. By default the linker will generate a file named <binary_name>.<extension>.manifest to describe the final binary. The linker does not embed a manifest file inside the binary and can only generate a manifest as an external file. There are several ways to embed a manifest inside the final binary, such as using the Manifest Tool (mt.exe) or compiling the manifest into a resource file. It is important to keep in mind that specific rules have to be followed when embedding a manifest inside the final binary to enable such features as incremental linking, signing, and edit and continue. These and other options are discussed in How to: Embed a Manifest Inside a C/C++ Application when building on the command line.
See Also
Manifests
/INCREMENTAL (Link Incrementally)
Strong Name Assemblies (Assembly Signing) (C++/CLI)
Edit and Continue
Understanding Manifest Generation for C/C++ Programs