Table of Contents
Advertisement
Windows Installer Editor Reference
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
If you have multiple exclusion lists, they are used in the following order:
If dotnetexclude.xml is on the local computer, it is used instead of the hard-coded
list.
If dotnetexclude.xml is on the share point directory, it becomes the primary
exclusion list, which overrides any local exclusion lists and the hard-coded list.
Use the following syntax in the XML file:
<<?xml version="1.0" encoding="utf-8"?>
<Exclusions>
<Assembly name="regular expression" />
</Exclusions>
The regular expression represents a wildcard in regular expression syntax. For
information on regular expression syntax, search for "Regular Expression Syntax" in the
MSDN Library (msdn.microsoft.com/library/).
The dotnetexclude.xml file overrides all the hard-coded exclusions. To retain the hard-
coded exclusions, add them to the XML file. The following list of default exclusions is
provided in the proper XML syntax. You can add your own exclusions to this list.
<<?xml version="1.0" encoding="utf-8"?>
<Exclusions>
<Assembly name="^Microsoft.VisualBasic$" />
<Assembly name="^Microsoft.VisualBasic.Vsa$" />
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 118.
Assembling an Installation
on
118
Advertisement
Table of Contents
Troubleshooting
