GenerateApplicationManifest Class
Assembly: Microsoft.Build.Tasks (in microsoft.build.tasks.dll)
'Declaration Public NotInheritable Class GenerateApplicationManifest Inherits GenerateManifestBase 'Usage Dim instance As GenerateApplicationManifest
public final class GenerateApplicationManifest extends GenerateManifestBase
public final class GenerateApplicationManifest extends GenerateManifestBase
Not applicable.
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 required an EntryPoint when generating an application manifest (assembly or native manifests do not require an EntryPoint). This requirement was enforced with the build error: "MSB3185: EntryPoint not specified for manifest."
In Visual Studio Code Name "Orcas", MSBuild will not issue this error when the EntryPoint task parameter is not specified. Instead, the <customHostSpecified> tag will be inserted as a child of the <entryPoint> tag, for example:
<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 assembly's references with a call to ResolveAssemblyReference.
-
Pass the output of the previous task and the assembly itself to ResolveManifestFiles.
Pass the dependencies via the Dependencies parameter to GenerateApplicationManifest.
Microsoft.Build.Utilities.Task
Microsoft.Build.Tasks.GenerateManifestBase
Microsoft.Build.Tasks.GenerateApplicationManifest
Windows 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition
The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.