Yes, You are absolutely wright! That is the problem...
Thank You

Best regards,
Peter G. Sakhno
C-MAP RUSSIA Ltd
http://www.c-map.ru/

Chesong Lee wrote:
> You may have to check if your custom action function has a correct function 
> prototype:
> 
> extern "C" 
> __declspec(dllexport) 
> UINT __stdcall MyCa(MSIHANDLE hInstall);
> 
> 1. extern "C" is required if your source code is C++.
> 2. __declspec(dllexport) is required if you do not have separate DLL 
> definition file
> 3. __stdcall is required if your default calling convention of the compiler 
> is __cdecl (default in Visual Studio is __cdecl)
> 
> Also, to debug your custom action, set environment variable MsiBreak to 
> "MyCA" (or name of the custom action) to attach to the MSI custom action 
> engine.
> 
> Regards,
> 
> Chesong Lee
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter G. Sakhno
> Sent: Wednesday, August 02, 2006 12:43 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Another question about MSM
> 
> Hello.
> 
> I have authored a custom action inside MSM and scheduled it, like that:
> <Binary Id="MyCA.dll" SourceFile="MyCA.dll"/>
> <CustomAction Id="MyCA" BinaryKey="MyCA.dll" DllEntry="MyCA"/>
> <InstallExecuteSequence>
>    <Custom Action="MyCA" After="LaunchConditions" /> 
> </InstallExecuteSequence>
> 
> In log I found that this action was performed.
> "
> MSI (s) (F4:50) [20:26:39:359]: Doing action: 
> MyCA.17DD507A_FE19_4C9D_9291_C4239315792A
> MSI (s) (F4:50) [20:26:39:359]: Note: 1: 2205 2:  3: ActionText
> Action start 20:26:39: MyCA.17DD507A_FE19_4C9D_9291_C4239315792A.
> MSI (s) (F4:C8) [20:26:39:390]: Invoking remote custom action. DLL: 
> C:\WINDOWS\Installer\MSI12.tmp, Entrypoint: MyCA
> MSI (s) (F4:FC) [20:26:39:390]: Generating random cookie.
> MSI (s) (F4:FC) [20:26:39:421]: Created Custom Action Server with PID 
> 1840 (0x730).
> MSI (s) (F4:64) [20:26:39:531]: Running as a service.
> MSI (s) (F4:70) [20:26:39:531]: Hello, I'm your 32bit Impersonated 
> custom action server.
> Action ended 20:26:39: MyCA.17DD507A_FE19_4C9D_9291_C4239315792A. Return 
> value 1.
> "
> But the function in dll was not called! That's for sure since that 
> function must show message box and message box was not shown.
> So what's wrong with that CA in MSM?
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to