GenerateApplicationManifest Class
This API supports the .NET Framework infrastructure and is not intended to be used directly from your code.
Implements the GenerateApplicationManifest task. Use the GenerateApplicationManifest element in the project file to create and execute this task. For usage and parameter information, see GenerateApplicationManifest Task.
MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0.
Inheritance Hierarchy
System.Object
Microsoft.Build.Utilities.Task
Microsoft.Build.Tasks.GenerateManifestBase
Microsoft.Build.Tasks.GenerateApplicationManifest
Namespace: Microsoft.Build.Tasks
Assembly: Microsoft.Build.Tasks.Core (in Microsoft.Build.Tasks.Core.dll)
Syntax
'Declaration
Public NotInheritable Class GenerateApplicationManifest _
Inherits GenerateManifestBase
public sealed class GenerateApplicationManifest : GenerateManifestBase
public ref class GenerateApplicationManifest sealed : public GenerateManifestBase
[<Sealed>]
type GenerateApplicationManifest =
class
inherit GenerateManifestBase
end
public final class GenerateApplicationManifest extends GenerateManifestBase
The GenerateApplicationManifest type exposes the following members.
Constructors
Name | Description | |
---|---|---|
GenerateApplicationManifest | Infrastructure. Initializes a new instance of the GenerateApplicationManifest class.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. |
Top
Properties
Name | Description | |
---|---|---|
AssemblyName | Infrastructure. Gets or sets the name of the assembly.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
AssemblyVersion | Infrastructure. Gets or sets the assembly version.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
BuildEngine | Gets or sets the instance of the IBuildEngine object used by the task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from Task.) | |
BuildEngine2 | Gets the instance of the IBuildEngine2 object used by the task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from Task.) | |
BuildEngine3 | Gets the instance of the IBuildEngine3 object used by the task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from Task.) | |
BuildEngine4 | Gets the instance of the IBuildEngine4 object used by the task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from Task.) | |
ClrVersion | Infrastructure. Gets or sets the minimum version of the Common Language Runtime (CLR) required by the application.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
ConfigFile | Infrastructure. Gets or sets the task item that contains the application configuration file.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
Dependencies | Infrastructure. Gets or sets an item list that defines the set of dependent assemblies for the generated manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
Description | Infrastructure. Gets or sets the manifest description text.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
EntryPoint | Infrastructure. Gets or sets the managed assembly or ClickOnce manifest reference that is the entry point to the manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
ErrorReportUrl | Infrastructure. Gets or sets the URL of the Web page that is displayed in dialog boxes during ClickOnce installations.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
FileAssociations | Infrastructure. Gets or sets a list of one or more file type that are associated with the ClickOnce deployment manifest. File associations only valid only when .NET Framework 3.5 or later is targeted.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
Files | Infrastructure. Gets or sets the full paths of files to include in the manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
HostInBrowser | Infrastructure. Gets or sets whether the application is hosted in a browser (as are WPF Web Browser Applications).MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
HostObject | Gets or sets the host object associated with the task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from Task.) | |
IconFile | Infrastructure. Gets or sets the application's icon file.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
InputManifest | Infrastructure. Gets or sets the input manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
IsolatedComReferences | Infrastructure. Gets or sets COM components to isolate in the generated manifest. MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
Log | Gets an instance of a TaskLoggingHelper class containing task logging methods.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from Task.) | |
ManifestType | Infrastructure. Gets or sets the type of manifest to generate. MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
MaxTargetPath | Infrastructure. Gets or sets the maximum manifest file name length.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
OSVersion | Infrastructure. Gets or sets the operating system (OS) version that is the minimum required by the application. MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
OutputManifest | Infrastructure. Gets or sets the generated manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
Platform | Infrastructure. Gets or sets the manifest platform.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
Product | Infrastructure. Specifies the ProductName property in the project file.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
Publisher | Infrastructure. Specifies the PublisherName property in the project file.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
RequiresMinimumFramework35SP1 | Gets or sets whether the application requires the .NET Framework 3.5 SP1.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
SuiteName | Infrastructure. Gets or sets the name of the folder on the Start menu where the application is located after ClickOnce deployment.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
SupportUrl | Infrastructure. Specifies the SupportUrl property in the project file.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
TargetCulture | Infrastructure. Gets or sets the manifest target culture code.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
TargetFrameworkMoniker | Gets or sets the target framework moniker.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
TargetFrameworkProfile | Gets or sets the target framework profile.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
TargetFrameworkSubset | Gets or sets the name of the .NET Framework subset to target.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
TargetFrameworkVersion | Infrastructure. The target .NET Framework version for the project.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
TrustInfoFile | Infrastructure. Gets or sets an XML document that specifies the application security.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
UseApplicationTrust | Infrastructure. Specifies whether the Product, Publisher, and SupportUrl properties are written to the application manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. |
Top
Methods
Name | Description | |
---|---|---|
AddAssemblyFromItem | Infrastructure. Adds an assembly reference to the manifest, based on the specified item.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
AddAssemblyNameFromItem | Infrastructure. Adds an assembly reference to the manifest, based on the specified item and the assembly reference type.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
AddEntryPointFromItem | Infrastructure. Adds an entry point reference to the manifest, based on the specified item and the assembly reference type.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
AddFileFromItem | Infrastructure. Adds a file reference to the manifest, based on the specified item.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
Equals | (Inherited from Object.) | |
Execute | Infrastructure. Executes the GenerateManifestBase task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
FindFileFromItem | Infrastructure. Returns the manifest file reference that matches the specified item.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
GetHashCode | (Inherited from Object.) | |
GetType | (Inherited from Object.) | |
ToString | (Inherited from Object.) | |
ValidateInputs | Infrastructure. Validates the inputs of the GenerateManifestBase task.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) | |
ValidateOutput | Infrastructure. Validates the generated manifest.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. (Inherited from GenerateManifestBase.) |
Top
Remarks
EntryPoint is an optional ITaskItem[] parameter that indicates the entry point for the generated manifest assembly. For a ClickOnce deployment manifest, this input specifies the ClickOnce application manifest.
In Visual Studio 2005, the GenerateApplicationManifest Task requires an EntryPoint when an application manifest is generated. (Assembly or native manifests do not require an EntryPoint.) This requirement is enforced by the build error "MSB3185: EntryPoint not specified for manifest."
In Visual Studio 2008, MSBuild does not issue this error when the EntryPoint task parameter is not specified. Instead, the <customHostSpecified> tag is inserted as a child of the <entryPoint> tag, for example, as follows.
<entryPoint xmlns="urn:schemas-
microsoft-com:asm.v2">
<co.v1:customHostSpecified />
</entryPoint>
You can add DLL dependencies to the application manifest by using the following steps:
Resolve the references in the assembly by using a call to ResolveAssemblyReference.
Pass the output of the previous task and the assembly itself to ResolveManifestFiles.
Pass the dependencies by using the Dependencies parameter to GenerateApplicationManifest.
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.