Suppose i have a custom action dll that is dependent on another dll. how to we incorporate this in installer. the dependent dll is load-time linked. placing this dll in support files does not appear to help.
Generally, if the custom action is in the Binary table, that means it will be running from %TEMP%, and SUPPORTDIR is a subfolder of %TEMP%, so this won't work.
My first response would be to statically link the custom action *.dll. Failing that you could always install the dependency to System32/%TEMP% as a prerequisite.
Call UseDll() on the dependencies first. When you load the dll that depends on another dll, if that dependency is already mapped in to the custom action process' memory space, then there will be no problem loading the dependency.
