I use InstallShield X Premier Edition.
I have .NET solution with 10 projects. And 1 (I will name it "BC") of these projects are used (referenced) in another 9 projects. Also I use third party .NET Win Controls in BC and some of other projects. When I build MSI dlls with third party controls are adding as dependencies of some component (I will name it "F"). But this component not directly references to third party controls. It references to component "BC". When I install my package and DON'T choose feature that contains component "F" then third party controls not being installed and other my EXE don't work.
If I remove component "F" then controls are being added as dependencies of another component ("SP") but not as dependencies of component "BC".
Is it InstallShield bug?
How I can correct this strange behaviour?
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
.NET dependencies
Started by
arokhin
, Nov 29 2004 19:31
1 reply to this topic