Re: [WiX-users] Custom action entrypoints
Hi Blair, Thanks for responding to my question. I tried several things and finally got it to work, although I still do not know what was going on. Originally I had all the CA names in question start with Create... After renaming them such that they all started with different words (such as Make..., Create, Do.. etc), they are now all executed by the installer. Thanks again! Miaohsi -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, November 08, 2010 10:02 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Custom action entrypoints I'm grasping at straws here but maybe it has something to do with the back-to-back loading of two different CA dlls into the sandbox? Did you look in the computer's event logs to see if there were any entries there that may explain why the second invocation failed? -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: Monday, November 08, 2010 9:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom action entrypoints Hi Christopher and anyone who can help, Thanks a lot for responding to my question. I am still having a problem trying to use two CustomActions.CA.dll written in C#. The CA's in the first one get called correctly but not those from the second one. When I use Depends.exe to view both dll's, I can see that all the CA's from both CustomActions.CA.dll are exported. However, when the install gets to calling the first CA in the second CustomActions.CA.dll, I get the 1723 error. Below is the install log file contents related to this problem. As you can see CA InstallTCL84 (from 1st CA dll) succeeded, but not Create_imr14cmd (from 2nd CA dll). Any idea? Thanks, Miaohsi Action 8:32:17: InstallTCL84. MSI (s) (90:34) [08:32:17:234]: Executing op: CustomActionSchedule(Action=InstallTCL84,ActionType=1025,Source=BinaryData,T arget=InstallTCL84,CustomActionData=INSTALLDIR=C:\SimSci2\;ROOTDIR=ROMeo60) MSI (s) (90:74) [08:32:17:234]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI29.tmp, Entrypoint: InstallTCL84 SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSI29.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CustomActions!CustomActions.ROMeoCustomActions1.InstallTCL84 MSI (s) (90:34) [08:32:23:781]: Executing op: ActionStart(Name=Create_imr14cmd,,) Action 8:32:23: Create_imr14cmd. MSI (s) (90:34) [08:32:23:796]: Executing op: CustomActionSchedule(Action=Create_imr14cmd,ActionType=1025,Source=BinaryDat a,Target=Create_imr14cmd,CustomActionData=COMPUTERNAME=USLKFQA03;INSTALLDIR= C:\SimSci2\;RootDir=ROMeo60;version=6.0) MSI (s) (90:90) [08:32:23:796]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2A.tmp, Entrypoint: Create_imr14cmd MSI (s) (90:34) [08:32:23:812]: Note: 1: 1723 2: Create_imr14cmd 3: Create_imr14cmd 4: C:\WINDOWS\Installer\MSI2A.tmp MSI (s) (90:34) [08:32:23:812]: Note: 1: 2205 2: 3: Error MSI (s) (90:34) [08:32:23:812]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1723: -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, November 03, 2010 1:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom action entrypoints I have multiple .CA.DLL files in my installer so I'm not sure what that problem is. As for the 16 entry points per DLL, I think I recall someone writing that they were able to alter the source to SfxCA ( EntryPoints.def and EntryPoints.h ) to get around that limitation. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Wang, Miaohsi" To: "wix-users@lists.sourceforge.net" Sent: Wed, November 3, 2010 2:56:39 PM Subject: [WiX-users] Custom action entrypoints Hello, I created a second custom action dll because of the max 16 entrypoint limit. I included the two CA dll's in my WiX install project as shown below: My problem is that it seems that the CA's in the second dll do not get recognized by MSI. For instance, CA "RestoreINSTALLDIR" below gets executed while CA "Create_imr14cmd" does not, and the install rolls back. When the second CA (Create_imr14cmd) is included in the CustomActions1.dll, it works fine. Once it is moved to the second dll, it does not get executed anymore and the install fails. Please let me know if you know how to lift the max 16 limit or if you know how to get the CA's in the second dll executed. Thank you so much for your help. Regards, Miaohsi *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individua
Re: [WiX-users] Custom action entrypoints
I'm grasping at straws here but maybe it has something to do with the back-to-back loading of two different CA dlls into the sandbox? Did you look in the computer's event logs to see if there were any entries there that may explain why the second invocation failed? -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: Monday, November 08, 2010 9:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom action entrypoints Hi Christopher and anyone who can help, Thanks a lot for responding to my question. I am still having a problem trying to use two CustomActions.CA.dll written in C#. The CA's in the first one get called correctly but not those from the second one. When I use Depends.exe to view both dll's, I can see that all the CA's from both CustomActions.CA.dll are exported. However, when the install gets to calling the first CA in the second CustomActions.CA.dll, I get the 1723 error. Below is the install log file contents related to this problem. As you can see CA InstallTCL84 (from 1st CA dll) succeeded, but not Create_imr14cmd (from 2nd CA dll). Any idea? Thanks, Miaohsi Action 8:32:17: InstallTCL84. MSI (s) (90:34) [08:32:17:234]: Executing op: CustomActionSchedule(Action=InstallTCL84,ActionType=1025,Source=BinaryData,T arget=InstallTCL84,CustomActionData=INSTALLDIR=C:\SimSci2\;ROOTDIR=ROMeo60) MSI (s) (90:74) [08:32:17:234]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI29.tmp, Entrypoint: InstallTCL84 SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSI29.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CustomActions!CustomActions.ROMeoCustomActions1.InstallTCL84 MSI (s) (90:34) [08:32:23:781]: Executing op: ActionStart(Name=Create_imr14cmd,,) Action 8:32:23: Create_imr14cmd. MSI (s) (90:34) [08:32:23:796]: Executing op: CustomActionSchedule(Action=Create_imr14cmd,ActionType=1025,Source=BinaryDat a,Target=Create_imr14cmd,CustomActionData=COMPUTERNAME=USLKFQA03;INSTALLDIR= C:\SimSci2\;RootDir=ROMeo60;version=6.0) MSI (s) (90:90) [08:32:23:796]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2A.tmp, Entrypoint: Create_imr14cmd MSI (s) (90:34) [08:32:23:812]: Note: 1: 1723 2: Create_imr14cmd 3: Create_imr14cmd 4: C:\WINDOWS\Installer\MSI2A.tmp MSI (s) (90:34) [08:32:23:812]: Note: 1: 2205 2: 3: Error MSI (s) (90:34) [08:32:23:812]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1723: -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, November 03, 2010 1:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom action entrypoints I have multiple .CA.DLL files in my installer so I'm not sure what that problem is. As for the 16 entry points per DLL, I think I recall someone writing that they were able to alter the source to SfxCA ( EntryPoints.def and EntryPoints.h ) to get around that limitation. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Wang, Miaohsi" To: "wix-users@lists.sourceforge.net" Sent: Wed, November 3, 2010 2:56:39 PM Subject: [WiX-users] Custom action entrypoints Hello, I created a second custom action dll because of the max 16 entrypoint limit. I included the two CA dll's in my WiX install project as shown below: My problem is that it seems that the CA's in the second dll do not get recognized by MSI. For instance, CA "RestoreINSTALLDIR" below gets executed while CA "Create_imr14cmd" does not, and the install rolls back. When the second CA (Create_imr14cmd) is included in the CustomActions1.dll, it works fine. Once it is moved to the second dll, it does not get executed anymore and the install fails. Please let me know if you know how to lift the max 16 limit or if you know how to get the CA's in the second dll executed. Thank you so much for your help. Regards, Miaohsi *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023).
Re: [WiX-users] Custom action entrypoints
Hi Christopher and anyone who can help, Thanks a lot for responding to my question. I am still having a problem trying to use two CustomActions.CA.dll written in C#. The CA's in the first one get called correctly but not those from the second one. When I use Depends.exe to view both dll's, I can see that all the CA's from both CustomActions.CA.dll are exported. However, when the install gets to calling the first CA in the second CustomActions.CA.dll, I get the 1723 error. Below is the install log file contents related to this problem. As you can see CA InstallTCL84 (from 1st CA dll) succeeded, but not Create_imr14cmd (from 2nd CA dll). Any idea? Thanks, Miaohsi Action 8:32:17: InstallTCL84. MSI (s) (90:34) [08:32:17:234]: Executing op: CustomActionSchedule(Action=InstallTCL84,ActionType=1025,Source=BinaryData,Target=InstallTCL84,CustomActionData=INSTALLDIR=C:\SimSci2\;ROOTDIR=ROMeo60) MSI (s) (90:74) [08:32:17:234]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI29.tmp, Entrypoint: InstallTCL84 SFXCA: Extracting custom action to temporary directory: C:\WINDOWS\Installer\MSI29.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CustomActions!CustomActions.ROMeoCustomActions1.InstallTCL84 MSI (s) (90:34) [08:32:23:781]: Executing op: ActionStart(Name=Create_imr14cmd,,) Action 8:32:23: Create_imr14cmd. MSI (s) (90:34) [08:32:23:796]: Executing op: CustomActionSchedule(Action=Create_imr14cmd,ActionType=1025,Source=BinaryData,Target=Create_imr14cmd,CustomActionData=COMPUTERNAME=USLKFQA03;INSTALLDIR=C:\SimSci2\;RootDir=ROMeo60;version=6.0) MSI (s) (90:90) [08:32:23:796]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2A.tmp, Entrypoint: Create_imr14cmd MSI (s) (90:34) [08:32:23:812]: Note: 1: 1723 2: Create_imr14cmd 3: Create_imr14cmd 4: C:\WINDOWS\Installer\MSI2A.tmp MSI (s) (90:34) [08:32:23:812]: Note: 1: 2205 2: 3: Error MSI (s) (90:34) [08:32:23:812]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1723: -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, November 03, 2010 1:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom action entrypoints I have multiple .CA.DLL files in my installer so I'm not sure what that problem is. As for the 16 entry points per DLL, I think I recall someone writing that they were able to alter the source to SfxCA ( EntryPoints.def and EntryPoints.h ) to get around that limitation. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Wang, Miaohsi" To: "wix-users@lists.sourceforge.net" Sent: Wed, November 3, 2010 2:56:39 PM Subject: [WiX-users] Custom action entrypoints Hello, I created a second custom action dll because of the max 16 entrypoint limit. I included the two CA dll's in my WiX install project as shown below: My problem is that it seems that the CA's in the second dll do not get recognized by MSI. For instance, CA "RestoreINSTALLDIR" below gets executed while CA "Create_imr14cmd" does not, and the install rolls back. When the second CA (Create_imr14cmd) is included in the CustomActions1.dll, it works fine. Once it is moved to the second dll, it does not get executed anymore and the install fails. Please let me know if you know how to lift the max 16 limit or if you know how to get the CA's in the second dll executed. Thank you so much for your help. Regards, Miaohsi *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -
Re: [WiX-users] Custom action entrypoints
I have multiple .CA.DLL files in my installer so I'm not sure what that problem is. As for the 16 entry points per DLL, I think I recall someone writing that they were able to alter the source to SfxCA ( EntryPoints.def and EntryPoints.h ) to get around that limitation. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Wang, Miaohsi" To: "wix-users@lists.sourceforge.net" Sent: Wed, November 3, 2010 2:56:39 PM Subject: [WiX-users] Custom action entrypoints Hello, I created a second custom action dll because of the max 16 entrypoint limit. I included the two CA dll's in my WiX install project as shown below: My problem is that it seems that the CA's in the second dll do not get recognized by MSI. For instance, CA "RestoreINSTALLDIR" below gets executed while CA "Create_imr14cmd" does not, and the install rolls back. When the second CA (Create_imr14cmd) is included in the CustomActions1.dll, it works fine. Once it is moved to the second dll, it does not get executed anymore and the install fails. Please let me know if you know how to lift the max 16 limit or if you know how to get the CA's in the second dll executed. Thank you so much for your help. Regards, Miaohsi *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Achieve Improved Network Security with IP and DNS Reputation. Defend against bad network traffic, including botnets, malware, phishing sites, and compromised hosts - saving your company time, money, and embarrassment. Learn More! http://p.sf.net/sfu/hpdev2dev-nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve Improved Network Security with IP and DNS Reputation. Defend against bad network traffic, including botnets, malware, phishing sites, and compromised hosts - saving your company time, money, and embarrassment. Learn More! http://p.sf.net/sfu/hpdev2dev-nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
