Windows Installer Editor Reference
399
Tools
Assembly dependencies that are in the exclusion list are never added to the installation,
even if the .NET assembly is rescanned, or if you add a new assembly that has the same
dependency. Use the Manage Assembly Exclusions tool to remove dependencies from
the exclusion list so that they can appear in future assembly scans.
To remove dependencies from the project dependency exclusion list
1. Open the installation.
2. On the Tools menu, click Manage Assembly Exclusions. (In Visual Studio: Project
menu > Manage Assembly Exclusions.)
3. In the Manage Assembly Exclusions dialog box, uncheck the check box for each
dependency to remove from the exclusion list.
4. Click OK.
See also:
How Assembly Dependencies are Added to an Installation
on page 138
About Dependency Scan Exclusions
on page 139
Manage Assembly Exclusions
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.
See
About Dependency Scan Exclusions
on page 139.
When you run the Manage Assembly Exclusions tool, the Manage Assembly Exclusions
dialog box lists all the dependencies that are in the exclusion list for the current
installation. You can uncheck the check box next to a dependency to remove it from the
exclusion list so that it can appear in future assembly scans.
See
Removing Dependencies from the Project Dependency Exclusion List
on page 398.
MSI to WSI Conversion
Use MSI to WSI Conversion to convert existing .MSI files to Windows Installer project
files (.WSI). An .MSI is a distributable installation. Because an .MSI typically
encapsulates all the files in the installation, it is larger and takes longer to save. A
project file (.WSI) compiles to an .MSI. Instead of compressed files, a .WSI contains
paths to source files. A .WSI file is smaller and you can set multiple options for the
output of the .MSI. For information on the differences between project files and
installation database files, see
Project Files and Database Files
on page 69.
If you have an installation .MSI, you can open and edit it in Windows Installer Editor.
However, to take advantage of some Windows Installer Editor features, you can convert
the .MSI to a project file.
See:
Converting an .MSI to a .WSI File
on page 400
Specifying Merge Module Source Directories
on page 401
Specifying File Source Directories
on page 402