Hi there,

I have a Custom Action DLL that I am currently working with to see if I can get it to actually function as intended. It seems I'm OK so far, but I do have a question...

I was thinking of using the same .dll with different functions for the various Custom Actions I might need. For example, I might want to check a registration code and set a property if it validates properly in the Immediate sequence. Then, in another function I want to have code to manipulate Custom Action Data. The action that calls this function would, of course, be scheduled in the Deferred Sequence.

Currently, all my code/actions appear to be working as intended.

I'm using Wise and it has an option to Call DLL from installation. However, when I create the two custom actions, there are two instances listed in the Resources (stuff in binary table). Is this the idea, that there would be binary source for each custom action or is there a way to reference the same binary resource for each action? Not that it is a big deal because the .dll is smallish, but I was just wondering.

I hope this is clear!!

Thanks in advance!!!
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Adding the same binary using example Wise will add duplicate binaries to the Binary table.
Just remove one of them in the Binary table and make sure to reference the one left for the CustomAction table entry.
Answered 03/01/2010 by: AngelD
Red Belt

Please log in to comment