Entry Point For Loader When Using Installshield 12

Add-in Express™ Support Service
That's what is more important than anything else

Entry Point For Loader When Using Installshield 12
 
Martin Mizzell




Posts: 77
Joined: 2006-06-02
Hi.

I am using Installshield 12 to build an installer for a v2.7 ADX addin with the loader. I cant seem to find where I set the "Entry Point" for registering the addin. Can anybody help?

Thanks.
Posted 18 Sep, 2006 15:42:01 Top
Todd Carlson




Posts: 29
Joined: 2006-05-07
Martin,
Define 3 custom actions:
1) RegisterADXDll
2) RollBackADXDll
3) UnInstallADXDll

The custom acctions should be MSI DLL (Installed with this package).

#1 should have a function name of DllRegister and use Deferred Execution
#2 should have a function name of DllUnregister and use Rollback Execution
#3 should have a function name of DllUnregister and use Deferred Execution

Since InstallShield does not allow you to create conditions for the MSI DLL actions, you will need to assign conditions to the custom actions in your sequence table (if you are doing a merge module it's another story). The conditions should be:

#1 $component_id_for_adxloaderdll > 2
#2 $component_id_for_adxloaderdll > 2
#3 $component_id_for_adxloaderdll = 2

HTH
Todd

Posted 18 Sep, 2006 16:51:41 Top
Martin Mizzell




Posts: 77
Joined: 2006-06-02
Ok, i have the three custom actions set up with the install execute sequence set to "AfterInstallFinalize".

Is the component id that you are talking about the same as the component code (the GUID for the component)?
Posted 18 Sep, 2006 17:00:26 Top
Todd Carlson




Posts: 29
Joined: 2006-05-07
Martin,
Sorry should have written that as

$(component_name)

Normally, when you add the adxloader.dll to IS12 it will create a component named adxloader.dll so the conditions would use $adxloader.dll

Todd
Posted 18 Sep, 2006 17:14:54 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
Joined: 2004-07-05
Hi Martin.

In InstallShield you just need to register the adxloader.dll as a COM component. Try to check the 'Self Register' option in the adxloader.dll properties.
Posted 19 Sep, 2006 07:20:27 Top