From: Mailinglist <Mai...@pr...> - 2007-09-10 07:29:29
|
Hello, Writing managed custom actions is not supported. A standalone executable wi= ll not see anything of the setup around. I took two half ready projects and used them, to build up something that gi= ves you the possibility to write managed custom actions and access the curr= ent setup from within your managed code, so you can e.g. post a return valu= e to a property in your setup. You can fetch the code and the samples under= the following link: http://www.forestwalk.de/?p=3D31 sorry, my entry is ju= st in German, but it's the latest link in the post you need. The source and= comments are in English though. If you need help in using this, feel free to ask back to me. Oliver From: wix...@li... [mailto:wix-users-bounces@lis= ts.sourceforge.net] On Behalf Of Rachna Khune Sent: Sonntag, 9. September 2007 04:53 To: wix...@li... Subject: [WiX-users] Managed custom action return values Hi there My custom action is a managed exe and I am attempting to do one of the two = choices below: 1) Show the exception messages from the custom action or be able to re= turn some error codes which I can log 2) Change the message that pops up when the custom action fails. The d= efault is "There is a problem with this windows...". Is there any way of ch= anging this default message? The Error attribute cannot coexist with the ExeCommand attribute in the Cus= tomAction element: Current implementation: <CustomAction Id=3D"InstallRepository" FileKey=3D"RepositorySetupCustomActi= ons.exe" ExeCommand=3D"create123 /InstallDir:"[INSTALLLOCATION]\"= " Return=3D"check" Impersonate=3D"no" Execute=3D"deferred" /> Seems as if writing managed custom actions is not preferred due to messages= popping up and not having access to the MSI thread. Thanks Rachna SDE Repository & Modeling Team, CSD Microsoft 425.705.6966 ra...@mi...<mailto:ra...@mi...> Cell: 425.533.1626 |