For closure, and all future google searches that end up here: the task
of getting my hands on a lib to just link into my action dll resulted
in my getting my hands on a merge module that just does everything for
me.
thanks everybody for your suggestions!
Oren
On Wed, Nov 19, 2008 at 4:25 PM, Rich
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 required, and
> then does a rollback?
You can't rollback features, only products.
The ty
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
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.
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
-Original Message-
From: Oren Mazor [mailto:
5 matches
Mail list logo
