Just to clarify, this behavior of executables is nothing to do with the
code being managed or not. Any executable that returns a non-zero exit
code to a custom action that checks the result will cause the "There is
a problem with this installer package" message and a rollback. It's
important to note that this is a result of the exit code, so just make
sure that an executable returns a zero exit code if it is successful.
The executable might work fine, but if it returns a non-zero exit code
it will fail the install.
To say "writing managed custom actions is not supported" is a rather
broad brush statement. There's nothing wrong with running managed code
executables that run in their own process space. It's the installer
class custom actions that are not supported by WiX - I don't believe WiX
cares if you fire off a managed code executable as a custom action.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rachna
Khune
Sent: Monday, September 10, 2007 8:43 AM
To: Mailinglist
Cc: (wix-users@lists.sourceforge.net)
Subject: Re: [WiX-users] Managed custom action return values
Thanks so much Oliver
I will take a look at it and ping you if I have any questions
danke
rachna
________________________________
From: [EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of Mailinglist
[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 12:29 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed custom action return values
Hello,
Writing managed custom actions is not supported. A standalone executable
will not see anything of the setup around.
I took two half ready projects and used them, to build up something that
gives you the possibility to write managed custom actions and access the
current setup from within your managed code, so you can e.g. post a
return value to a property in your setup. You can fetch the code and the
samples under the following link: http://www.forestwalk.de/?p=31 sorry,
my entry is just 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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rachna
Khune
Sent: Sonntag, 9. September 2007 04:53
To: wix-users@lists.sourceforge.net
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
return some error codes which I can log
2) Change the message that pops up when the custom action fails.
The default is "There is a problem with this windows...". Is there any
way of changing this default message?
The Error attribute cannot coexist with the ExeCommand attribute in the
CustomAction element:
Current implementation:
<CustomAction Id="InstallRepository"
FileKey="RepositorySetupCustomActions.exe" ExeCommand="create123
/InstallDir:"[INSTALLLOCATION]\"" Return="check"
Impersonate="no" Execute="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 [EMAIL PROTECTED]
Cell: 425.533.1626
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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
