Hmm.. I've only tried it with unmanaged code.  Plus, I used that approach 
because the custom DLL came from a third party and I had no control over it.  
Using this technique with managed code will bring a whole extra layer of 
complexity.

Calling managed code from a CA (or rather, the numerous reasons for not doing 
so) has been discussed at length on this list. Please consult the archives (and 
Rob M's blog) for more information.

If at all possible, you should consider re-writing your custom DLL as unmanaged 
code.

Paul.

-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de BugBoy
Envoyé : 10 mars 2008 02:09
À : wix-users@lists.sourceforge.net
Objet : Re: [WiX-users] Use multiple files during CustomAction


Good idea. It's quite an amount of work (I use managed code), but I'll give
it a try. I think it's a flaw in the MSI design...


Paul Lalonde-2 wrote:
> 
> You could embed the custom DLL in your CA's resources, then specify  
> when linking the CA that the DLL is delay-loaded. At runtime, the CA  
> could extract the DLL and put it in the TEMP directory. You could then  
> supply a callback to the delay-load infrastructure in order to load  
> the DLL from the TEMP dir.
> 
> I've used this approach successfully myself. There's documentation on  
> delay-loading available in MSDN.
> 
> Hope this helps,
> 
> -- 
> Paul Lalonde                       paullalonde at mac dot com
> "Il n'y a que les banques qui sont libres" -- Jean-Luc Godard
> 
> 
> Le 08-03-09 à 19:05, BugBoy a écrit :
> 
>>
>> This is bad, because I run it only during uninstall and this code is  
>> run at
>> the end of the uninstall, so the dependencies are not there anymore. I
>> really think this is bad. Because of UAC I need to use deferred  
>> execution :(
>>
>>
>> Alexander Shevchuk wrote:
>>>
>>> Custom actions stored in Binary table must be either self-contained  
>>> or
>>> depend on pre-installed items.  Because you run your  
>>> UninstallAction after
>>> InstallFiles action you can just include your dependency dll into  
>>> your
>>> install.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Use-multiple-files-during-CustomAction-tp15946177p15950563.html
Sent from the wix-users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to