Table of Contents
Advertisement
Windows Installer Editor Reference
See also:
How Assembly Dependencies are Added to an Installation
About Dependency Scan Exclusions
When you add a .NET assembly to an installation, Windows Installer Editor can scan the
assembly's manifest for dependencies and either add the dependencies to the
installation or prompt you to select the dependencies to add.
You can use the following exclusion lists to exclude dependencies from assembly scans:
Project dependency
exclusion list
Global dependency
exclusion list
Assembly dependencies that are in an exclusion list are never added to an installation,
even if the .NET assembly is rescanned, or if you add a new assembly that has the same
dependency.
About the Global Dependency Exclusion List
By default, certain dependencies are excluded from assembly scans in all .NET
installations. These global dependency exclusions are hard-coded.
You can create an XML file that overrides the hard-coded dependency exclusions with
exclusions that you define. Name the file dotnetexclude.xml and place it in one of the
following locations:
The Windows Installer Editor subdirectory of this product's installation directory on
the local computer
The top level of the share point directory
A project dependency exclusion list is maintained for every
.NET installation project. A dependency is added to the list
when you choose not to include the dependency during an
assembly scan.
Use this exclusion list to exclude specific dependencies from
a single installation.
You can remove dependencies from the project dependency
exclusion list.
See
Removing Dependencies from the Project Dependency
Exclusion List
on page 398.
By default, certain dependencies are excluded from
assembly scans in all .NET installations. These global
dependency exclusions are hard-coded.
You can create an XML file that overrides the hard-coded
dependency exclusions with exclusions that you define.
Use this exclusion list to exclude specific dependencies, or
dependencies that match a wildcard, from all installations.
For example, dependency files that are part of the .NET
Framework.
See
About the Global Dependency Exclusion List
page 139.
Assembling an Installation
on page 138
on
139
Advertisement
Table of Contents
Troubleshooting
