Re: [WiX-users] daisy chaining DLLs in custom actions

, Richard <[EMAIL PROTECTED]> wrote: > > In article <[EMAIL PROTECTED]>, >"Oren Mazor" <[EMAIL PROTECTED]> writes: > >> what about creating a separate feature+component that installs that >> DLL into the temp folder, somewhere, does the evaluation

Re: [WiX-users] daisy chaining DLLs in custom actions

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 coul

[WiX-users] daisy chaining DLLs in custom actions

hi all, I'm trying to do a system verification step as part of my install, but I've encountered a small problem with the standard custom action dll solution. I've created a CustomActions.dll to contain a isValidSystem call. unfortunately, the algorithm to validate the system is inside yet another