When multiple projects reference a single assembly, and the projects' primary outputs are added to different directories in the setup project, the referenced assembly is placed in only one of the folders. Another way to explain it:
Situation: Project A references MyLibrary.dll Project A's primary output is added to the base installation directory.
Project B references MyLibrary.dll Project B's primary output is added to a subdirectory of the installation.
Problem: MyLibrary.dll is placed in only Project A OR Project B's directory, not both as I would expect.
MyLibrary.dll shows in both primary output's "Dependencies from scan at build..." dialog box, so it recognized there is a dependency.
I have this exact same problem. Is there a resolution for this? For now, the only way I've found to do this is to turn off dependency checking on all the .NET assemblies and then manage the dependency file addition manually.
