We recommend using Visual Studio 2017

/MANIFEST (Create Side-by-Side Assembly Manifest)


The latest version of this topic can be found at -MANIFEST (Create Side-by-Side Assembly Manifest).


## Remarks  
 /MANIFEST specifies that the linker should create a side-by-side manifest file. For more information about manifest files, see [Manifest Files Reference](http://msdn.microsoft.com/library/aa375632).  
 The default is /MANIFEST.  
 The /MANIFEST:EMBED option specifies that the linker should embed the manifest file in the image as a resource of type RT_MANIFEST. The optional `ID` parameter is the resource ID to use for the manifest. Use a value of 1 for an executable file. Use a value of 2 for a DLL to enable it to specify private dependencies. If the `ID` parameter is not specified, the default value is 2 if the /DLL option is set; otherwise, the default value is 1.  
 Beginning with [!INCLUDE[vs_orcas_long](../Token/vs_orcas_long_md.md)], manifest files for executables contain a section that specifies User Account Control (UAC) information. If you specify /MANIFEST but specify neither [/MANIFESTUAC](../Topic/-MANIFESTUAC%20\(Embeds%20UAC%20information%20in%20manifest\).md) nor [/DLL](../Topic/-DLL%20\(Build%20a%20DLL\).md), a default UAC fragment that has the UAC level set to *asInvoker* is inserted into the manifest. For more information about UAC levels, see [/MANIFESTUAC (Embeds UAC information in manifest)](../Topic/-MANIFESTUAC%20\(Embeds%20UAC%20information%20in%20manifest\).md).  
 To change the default behavior for UAC, do one of these:  
-   Specify the /MANIFESTUAC option and set the UAC level to the desired value.  
-   Or specify the /MANIFESTUAC:NO option if you do not want to generate a UAC fragment in the manifest.  
 If you do not specify /MANIFEST but do specify [/MANIFESTDEPENDENCY](../Topic/-MANIFESTDEPENDENCY%20\(Specify%20Manifest%20Dependencies\).md) comments, a manifest file is created. A manifest file is not created if you specify /MANIFEST:NO.  
 If you specify /MANIFEST, the name of the manifest file is the same as the name of your output file, but with .manifest appended to the file name. For example, if your output file name is MyFile.exe, the manifest file name is MyFile.exe.manifest.  If you specify /MANIFESTFILE:*name*, the name of the manifest is what you specify in *name*.  
### To set this linker option in the Visual Studio development environment  
1.  Open the project's **Property Pages** dialog box. For details, see [How to: Open Project Property Pages](../Topic/How%20to:%20Open%20Project%20Property%20Pages.md).  
2.  Expand the **Configuration Properties** node.  
3.  Expand the **Linker** node.  
4.  Select the **Manifest File** property page.  
5.  Modify the **Generate Manifest** property.  
### To set this linker option programmatically  
1.  See [GenerateManifest](assetId:///P:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.GenerateManifest?qualifyHint=False&autoUpgrade=True).  
## See Also  
 [Setting Linker Options](../Topic/Setting%20Linker%20Options.md)   
 [Linker Options](../Topic/Linker%20Options.md)