In IS 11.5, I have some problems with self-registering DLLs, and the DLL they link to implicitely.
It seems that "Feature B depends on Feature A" does not mean, A gets installed before B, and uninstalled after B.
Is there any way to control order of installation? The DLLs of A just need to be present in the target when B's DLLs get registered or unregistered.
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.
Install order vs. dependencies
Started by
peterchen
, Aug 22 2006 14:36
1 reply to this topic
Glytzhkof
-
- Moderators
- 1,447 posts
Posted 22 August 2006 - 16:44
Normally you use the "Extract COM data from DLL" feature to ensure that such dependencies do not cause problems during deployment - please note that the extraction can fail sometimes due to the dependencies as well.
You can also use a custom action to run regsvr32.exe in the order you need. Wise and Installshield generally also have ways to specifiy the order of self registration, but COM extraction is generally much better.
You can also use a custom action to run regsvr32.exe in the order you need. Wise and Installshield generally also have ways to specifiy the order of self registration, but COM extraction is generally much better.
Regards
-Stein Åsmul
-Stein Åsmul