When I compile a Basic Msi project that contains a file, A.DLL, which has a dependency, B.DLL, but B.DLL is *not* in the list of components I'm installing, InstallShield 2011 will automatically search for the file and include it in the list of files to be installed on the customer's computer.
Is there a way to disable this behavior, at least for that project? For reasons that would take too long to explain, I do not want the B.DLL dependency to be installed, just A.DLL. I can't find a way to make the compiler do this.
This behavior typically occurs if the files in a component are .NET assemblies and the containing component's .NET Scan At Build setting is set to Dependencies and Properties. Changing this to Properties Only will turn of the dependency scan per-component.
