This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- How to add actions depending on the result dll functions?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 03, 2009
08:55 AM
How to add actions depending on the result dll functions?
Hi,
I want to call DLL function using install shield's basic MSI project which checks some application already installed or not. If not then I want install that application.
Can I use custom action and sequence for that?
I used custom action to call the function from DLL. But what about their result checking and taking action?
Please tell me, How to achieve this using insatall shield 2009.
Thanks & Regards
Varsha
I want to call DLL function using install shield's basic MSI project which checks some application already installed or not. If not then I want install that application.
Can I use custom action and sequence for that?
I used custom action to call the function from DLL. But what about their result checking and taking action?
Please tell me, How to achieve this using insatall shield 2009.
Thanks & Regards
Varsha
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 03, 2009
09:57 PM
If that's all you want to do, you probably don't even need to call a function inside of a DLL.
You could run a SystemSearch to look for the other application, either by checking the value (or existence) of a registry value or looking for the presence (or absence) of a file. This will set a public property that can then be used in a Install Condition and bail out of your installation appropriately.
If for some reason you do want to call your function in a custom action, you would use a similar technique, only have your function set the value of a property that can then be tested by a subsequent action.
You could run a SystemSearch to look for the other application, either by checking the value (or existence) of a registry value or looking for the presence (or absence) of a file. This will set a public property that can then be used in a Install Condition and bail out of your installation appropriately.
If for some reason you do want to call your function in a custom action, you would use a similar technique, only have your function set the value of a property that can then be tested by a subsequent action.