4 replies to this topic

[Majd]

Hi,

I am probably not using InstallShield right. I am trying to make a setup program that would register about 20 DLL's. These DLL's have to be in a specific order due to some dependencies between them.  I have tried for so long with installShield but I could not put them in the right order.  I would thank everyone for help..

[Irina]

Hi,
I am not sure that it is a best way, but you can create a custom action for each yours Dll from the Custom Action Wizard:
Type: launch an executable
Location: Installed with the product
Source  [DllName]
Target  /REGSERVER
Set the type of custom actions as Deferred.
Insert these custom action on the right order in the execute sequence.

[Majd]

Quote

Quote: from Irina on 10:19 pm on Aug. 21, 2001 Hi, I am not sure that it is a best way, but you can create a custom action for each yours Dll from the Custom Action Wizard: Type: launch an executable Location: Installed with the product Source  [DllName] Target  /REGSERVER Set the type of custom actions as Deferred. Insert these custom action on the right order in the execute sequence.

[Ian Blake]

Msi gives you a great deal of control over component registration.  You should be able to author the Class, AppID, and Registry tables to take full account of all interdependancies between objects.  This may be a lot of work.  The tools within ISWI will help you author these tables.  You may need to do fine tuning yourself.

If you follow Irina's idea remember to write actions to handle rollback,. uninstall and upgrades etc. in a correct manner.  When you have thought through these you will understand why self registration is not always a good idea.