Navigation: Actions > Microsoft .NET > Manifest Generator > Manifest Generator Action Options Tab |
|
This tab of the Manifest Generator action configures additional options.
Populate from directory: Populates the application manifest with descriptions of all assemblies and files found in the path to directory containing the application you want to deploy (application manifests only). For each file in the directory, Mage.exe decides whether the file is an assembly or a static file. If it is an assembly, it adds a <dependency> tag and installFrom attribute to the application with the assembly's name, code base, and version. If it is a static file, it adds a <file> tag. Mage.exe will also use a simple set of heuristics to detect the main executable for the application, and will mark it as the ClickOnce application's entry point in the manifest. Mage.exe will never automatically mark a file as a "data" file; this must be done manually.
Mage.exe also generates a hash for each file based on its size. ClickOnce uses these hashes to ensure that no one has tampered with the deployment's files since the manifest was created. If any of the files in your deployment change, you can run Mage.exe with the Update command and this option, and it will update the hashes and assembly versions of all referenced files.
This option will include all files in all subdirectories found within the path.
If you use this option with the Update command, Mage.exe will remove any files in the application manifest that no longer exist in the directory.
Output filename: Specifies the output path of the file that has been created or modified (optional). If not supplied when using the New command, the output is written to the current working directory with a default file name, whose exact name depends upon the type of file you create:
• | Deployment: deploy.application |
• | Application: application.exe.manifest |
If this option is not supplied when using the Update command, Mage.exe will write the file back to the input file.
Trust level: Specifies the trust level of the application.
Use manifest for trust: Whether to use a manifest for the trust info.
Override executable filename: Overrides the default executable (mage.exe). If not specified, the 32-bit edition of Visual Build calls the 32-bit version of mage.exe, and the 64-bit edition of Visual Build calls the 64-bit version of mage.exe if available.
Additional command-line options: Use this field to enter any additional command-line options to be added to the call that is constructed (optional).