Manifest maker now includes a command line project build tool.
uses the same project file as the GUI and creates the same output. You can
create project files using the GUI then run the command line builder either
standalone or integrated into your build process.
sxs32cmd.exe command line syntax
Syntax: sxs32cmd [options] <project-file-path>
- Perform manifest auto-fix, default: 1
- Pause before exiting the program, default: 0
- Build even if CLR DLLs present and no CLR available, default: 0
- Copy DLL files instead of moving, default: 0
- Enable trace, default: 1
- Path to the program trace file, default:
- Trace level (between 0 and 9), default: 2
- Embed manifest as '#number' resource, default: none
In the past this option only controlled CLR manifests. Starting with version
4.0 it also applies to COM, DLL and EXE manifests.
- Erase manifest file after embedding, default: 1
applies if the manifest is being embedded, ignored otherwise.
- Build a manifest fragment, path: full path to the manifest file. See Visual Studio integration for more information.
- Get assembly version from this file (EXE or DLL).
- Build a manifest fragment, manifest search root folder: folder in which
Windows looks for private assemblies used by the fragment. Default: project
- Destination folder: overrides the folder saved in the project.
processorArchitecture attribute. Valid values are
amd64. To allow easy integration with Visual Studio Manifest Maker also
accepts the value of
$(PlatformName) command macro (
win32 is treated as x85
and x64 is treated as amd64).
- Write multiple type libraries in <file name='abc.dll\n'> tags, default: 0.
- Use generic processor type in assembly references, default: 0.
- Use PSDispatch proxy instead of PSOAInterface, default: 0.
- Use 'runtimeVersion' for CLR build; clear: '/o:-', recommended: '/o:auto'.
- Update private assembly reference identities, default: 0.
- Compress shared assembly files into the MSI file, default: registry
This option is only used when building a shared assembly and ignored in other
cases. If this option is selected only distribute the MSI file from the
target folder. If this option is not selected distribute the entire content
of the target folder.
- Relative file loading; default: setting from the user's registry.
Valid values are:
0 = no relative paths used, only absolute paths (compatible with Manifest maker 1.* and 2.0)
1 = try path relative to project folder first, then target folder then absolute path
(compatible with version 2.3)
2 = try path relative to target folder first, then project folder then absolute path
- Quiet mode, Visual Studio compatible messages only.
- Help summary
Additionally the following options are intended for integrated builds:
- Build a COM manifest for this DLL (normally #1)
- Build a CLR manifest for this DLL (normally #1)
- Build a DLL manifest
for this DLL (normally #2 or #3)
- Build an application manifest
for this program (normally #1)
For convenience, if /dll is used with a
program, it is silently changed to /exe and a /com used with a .Net DLL is
silently changed to /clr. In effect /dll can be used for REF-manifests and /com
If more than one of the above options is specified, the last
one wins. The project file path is optional. However, if there is no project
file for a /dll or /exe build, the resulting manifest will be empty. For /clr
and /com builds, the project file is ignored.
The following options modify build specific settings for the module
selected one of the options above:
- Use source path, CLR DLLs only.
- Use current registration, COM DLLs only.
- Run self registration with full privileges, COM DLLs
- Override file use of the above DLL; valid values:
* = default
n = ignore
o = other file
c = CLRclass
d = DLLmanifest
Manifest Maker may silently ignore incompatible
Options are case insensitive and can be specified in any
order. Duplicate options are allowed - next value overrides the previous
value. There may be only one project file path and it must be enclosed in
quotes if it contains spaces. This program returns zero on success and an
error code on failure.
To create a COM or CLR manifest in a Visual Studio or
MSBuild build environment use:
Do not use sxs32mm
project file for building DEF manifests using /com or /clr.
To create an application manifest of a DLL REF manifest use:
where Inputs is a placeholder for the MSBuild item with the *.sxs32mm project file.
When building both DEF and REF manifests for a DLL, build the REF manifest first.
Options are case insensitive and can be specified in any order. Duplicate
options are allowed - next value overrides the previous value. There may be
only one project file path and it must be enclosed in quotes if it contains
spaces. This program returns zero on success and an error code on failure.
Read more on using command line Manifest Maker with Visual Studio and MSBuild.