ClickOnce Deployment on Windows Vista
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, use the version selector at the top left. We recommend upgrading to Visual Studio 2019. Download it here
Building applications in Visual Studio for User Account Control (UAC) on Windows Vista normally generates an embedded manifest, encoded as binary XML data in the application's executable file. Because ClickOnce and Registration-Free COM applications require an external manifest, Visual Studio generates a file for these types of projects containing the UAC data instead of an embedded manifest. By default, Visual Studio uses information from a file called app.manifest to generate external UAC manifest information (for ClickOnce and Registration-Free COM deployment), or to embed it in the application's executable file (for all other cases). Visual Studio provides the following options for manifest generation:
Use an embedded manifest. Embed UAC data in the application's executable file and run as normal user.
This is the default setting (unless you use ClickOnce). This setting will support the usual manner in which Visual Studio operates on Windows Vista; that is, the generation of an internal and external manifest, both using
Use an external manifest. Generate an external manifest by using app.manifest.
This generates only the external manifest by using the information in app.manifest. When you publish an application by using ClickOnce or Registration-Free COM, Visual Studio adds app.manifest to the project and adds this option.
Use no manifest. Create the application without a manifest.
This approach is also known as virtualization. Use this option for compatibility with existing applications from earlier versions of Visual Studio.
The new properties are available on the Application page of the Project Designer (for Visual C# projects only) and in the MSBuild project file format.
Note that the method for configuring UAC manifest generation in the Visual Studio IDE differs depending on project type (Visual C# and Visual Basic).
For information about configuring Visual C# projects for manifest generation, see Application Page, Project Designer (C#).
For information about configuring Visual Basic projects for manifest generation, see Application Page, Project Designer (Visual Basic).