Reviewing .NET Dependency Scanner Results

InstallShield 2018

Project • This information applies to the following project types:

Basic MSI
DIM
InstallScript
InstallScript MSI
Merge Module

InstallShield offers different built-in methods for identifying dependencies of .NET assemblies. If you use these built-in methods, the scanning may identify as a dependency a file or merge module that is not required by your product. If you are using the Static Scanning Wizard and that occurs, you can specify in the wizard that you do not want to add that dependency to your project. If you are using the .NET scan at build functionality to automatically include any possible .NET dependencies in your project at build time, you can change the values of the component’s settings so that the .NET assembly is not scanned for dependencies automatically:

In Basic MSI, InstallScript MSI, and Merge Module projects, InstallShield scans each component’s .NET assembly for dependencies automatically at build time by default. You can override this default behavior by changing the value of a component’s .NET Scan at Build setting as needed.
In InstallScript projects, InstallShield does not scan each component’s .NET assembly for dependencies at build time by default. You can override this default behavior by changing the values of a component’s .NET Assembly setting and its .NET Scan at Build setting as needed.

In addition, InstallShield enables you to specify on a machine-wide basis any files that you want to be included or excluded automatically any time that you perform a dependency scan through InstallShield. For more information, see Filtering Files in Dependency Scanners.

To obtain the best results when you are trying to identify dependencies, it is recommended that you thoroughly test your product and its installation on a clean machine. If your product does not behave as expected, determine whether any dependencies are missing from the machine, and if so, whether they should be included in the installation.

See Also