Re: [WiX-users] CustomAction not being called

2006-10-18 Thread Bob Arnson
Jeff Jones (HS) wrote: > The operation I am doing should be run as the person that is doing the > installation. How do I avoid the impersonation? > The default is to impersonate the user, so you only need Impersonate="no" when you want the CA to run as LocalSystem. -- sig://boB http://bobs.

Re: [WiX-users] CustomAction not being called

2006-10-18 Thread Jeff Jones (HS)
r the help Jeff From: Bob Arnson [EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 5:39 PM To: Jeff Jones (HS) Cc: Arnette, Bill; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] CustomAction not being called Jeff Jones (HS) wrote: > That doesn&#

Re: [WiX-users] CustomAction not being called

2006-10-18 Thread Bob Arnson
Jeff Jones (HS) wrote: > That doesn't seem to be the issue. 'dumpbin /EXPORTS WildcaddySetup.dll' > shows: > Take a look at 'dumpbin /imports' -- the most common cause of CAs failing to load is a missing dependency. CAs in the Binary tables are extracted to a temporary directory so they don

Re: [WiX-users] CustomAction not being called

2006-10-18 Thread Jeff Jones (HS)
ists.sourceforge.net Subject: RE: [WiX-users] CustomAction not being called Make sure that is the entry point of the DLL. An exported __stdcall function is actually decorated to be [EMAIL PROTECTED] so try setting DllEntry to [EMAIL PROTECTED] If that works, you can alias the export with the

Re: [WiX-users] CustomAction not being called

2006-10-18 Thread Arnette, Bill
Make sure that is the entry point of the DLL. An exported __stdcall function is actually decorated to be [EMAIL PROTECTED] so try setting DllEntry to [EMAIL PROTECTED] If that works, you can alias the export with the with /EXPORT:[EMAIL PROTECTED] option on the linker command line. Use: dumpbin