How can I tell InstallShield about assembly dependencies which are not referenced but used by dependency injection with unity?

My MSI setup built by InstallShield 2011 (Stand alone version on a TFS) does not include all the required assemblies. The assemblies are not directly referenced in the project but injected dynamically by dependency injection with Unity.

It looks like InstallShield does not recognize the required assemblies, can't resolve the dependencies. Using Reflector shows quite the same sparse result for the dependencies.

So my question is: How can I tell InstallShield about these not referenced but required a开发者_JAVA百科ssemblies?

I would suggest just adding the assemblies to your InstallShield project. Project Output Groups and Dependency Scans at Build are both fragile; they can cause unexpected and unwarned changes to your installer that break minor upgrade rules. It's still probably useful to leave the Properties scan in place, however.

If you only have one implementation assembly you end up shipping, just have the application reference it. If not, Michael would have the better answer.