what about creating a separate feature+component that installs that DLL into the temp folder, somewhere, does the evaluation required, and then does a rollback?
actually, that may not be possible, since my custom actions need to occur before launch conditions, which occurs before any features could be installed. On Wed, Nov 19, 2008 at 11:22 AM, Kelly Leahy <[EMAIL PROTECTED]> wrote: > Oren, you should include tools.dll as a resource inside CustomActions.dll > (or just include it at the end of the file using some mechanism whereby > you can pull it back out), and then extract it to a temp folder during > your initial processing in CustomActions.dll and load it using > LoadLibrary. > > Unfortunately that's not much of an option for me. I was hoping there was a built in way that I was just missing, but I guess not. On Wed, Nov 19, 2008 at 11:26 AM, Brian Simoneau <[EMAIL PROTECTED]> wrote: > If you own the code for tools.dll, you can change it to a library and > link the library in CustomActions.dll. Otherwise, you will have to > extract tools.dll onto the system before using it. There is no built-in > way to do this. > > -Brian Simoneau ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
