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

My MSI setup, created by InstallShield 2011 (stand-alone version on TFS), does not contain all the required builds. Assemblies are not directly referenced in the project, but are dynamically injected by injecting dependencies with Unity.

It seems that InstallShield does not recognize the necessary assemblies, cannot resolve dependencies. Using Reflector shows the same sparse result for dependencies.

So my question is: how can I tell InstallShield about these unrelated but required builds?

+4
source share
2 answers

I would suggest just adding assemblies to your InstallShield project. Groups of project results and build dependency checks are fragile; they can cause unexpected and unreasonable changes in your installer that violate minor update rules. However, it is probably useful to leave the property scan in place.

+4
source

If you have only one assembly assembly, you end up sending it, just provide its link to the application. If not, Michael would have a better answer.

+1
source

Source: https://habr.com/ru/post/1346205/


All Articles