Project Properties Dialog - Build
|user interface | home
The full list of available build types:
This is the project's destination directory also referenced to as the target directory. All project files are copied or written to this directory or subdirectories of this directory. Some files may be moved from the target directory to the assembly subdirectory. This is necessary for the private or shared assembly to work. If a copy of such file is required in the target directory, just copy the file (do not move) from the assembly subdirectory back to the target directory.
These three fields are used to make the assembly name. See Step-by-Step Guide for more information on assembly names.
This is the private or shared assembly version. Note that application manifests versions are always derived from the application version resource.
Windows version resource actually contains four version numbers:
Manifest Maker uses the binary file version.
Processor architecture for which this project will be built. All files (DLLs, programs, manifests and shared assemblies) that do not match this processor type will be ignored during the build.
Manifest Maker recognizes three processor types, but only supports building manifests for the standard 32-bit x86 and the 64-bit amd64 (Intel's EM64T) architectures. The Any CPU choice is intended for CLR and advanced builds. A manifest built by Manifest Maker will only contain modules and assembly references for the architecture selected in the project properties dialog. All other files are ignored.
Note that you need to run Manifest Maker on a 64-bit x64 system to build 64-bit manifests.
By default Manifest Maker recognizes embedded resource manifests. During build DLLs with embedded manifests are treated as assemblies. No manifests are built for them but, instead, the embedded manifests are referenced. If you check this option Manifest Maker ignores the embedded manifest resource and treats the DLL as if it did not contain embedded manifests.