Cool, thanks for the link to Runtime.wxi . That definitely should save lots of 
time, effort, and aggravation in figuring all those
properties out.

Regarding "using Custom Actions is an admission of failure" (
http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-an-admission-of-failure
 ), I believe our case is a
combination of the blog post's points. I'll describe our context, since it may 
be worth mentioning why our installer is a "failure"
(and maybe find a way to correct it).

Our system being installed is written in Java, but it needs to run as a service 
on the client. Had I been on the project from the
beginning, I would have opted for C# (and probably wouldn't be writing this 
e-mail right now, since I'd expect C# software to be
easier to implement as a service).

So we need custom actions because:
* We don't have the time or budget to re-write the whole thing from scratch in 
C# or something more service-friendly.
* Java programs (or batch files that may execute them) can't run as services, 
so we need to use a wrapping tool (Java Service
Launcher, http://sourceforge.net/projects/jslwin/), which runs as an .exe, 
which needs a custom action to install, start, stop, and
remove the services.

So yeah, it's a piecemeal, hacky, suboptimal solution, but if software 
engineering could ever be done perfectly within time and
budget constraints, I can't speak for anyone else, but I'd definitely be much 
happier. Still, I'm glad you brought it up, because it
at least gave me pause to question whether or not we really need to use CAs, 
since simpler solutions are preferable. Unfortunately,
I don't know of any alternatives, given our situation. If you have any 
suggestions on how to do what I've described better or more
easily, we're definitely open to suggestions.

Alain

-----Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: March 8, 2013 07:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Running EXEs at install and uninstall

There's more than just Install, Uninstall & Repair to consider for your custom 
actions. dblock (creator of dotnetinstaller) has a
handy WiX include you can use to save time writing all the conditions yourself 
->
http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance

Also 
http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-an-admission-of-failure

Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the <Virtual Environment>** Integrated 
Environmental Solutions Limited. Registered in Scotland
No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, 
Glasgow G20 0SP Email Disclaimer 


-----Original Message-----
From: Alain Forget [mailto:afor...@cmu.edu] 
Sent: 08 March 2013 12:16
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Running EXEs at install and uninstall

Thank you. You bought up something I hadn't considered: repairs. So on a 
repair, I would like the uninstall exes AND the install
exes to run. Suggestions on how to make that happen with inner text conditions?

Alain

-----Original Message-----
From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net]
Sent: March 8, 2013 03:32
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Running EXEs at install and uninstall

On 07/03/2013 19:37, Alain Forget wrote:
> 2) I only want the InstEXEs to run during installation (and not when 
> uninstalling). Thus, since there is the special REMOVE="ALL" to denote 
> "do this only if uninstalling", is there an equivalent I
need to use to specify "do this only if installing"?

Use "NOT Installed".
N.B. This condition will mean your actions won't run during a repair.

Rob



------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the 
endpoint security space. For insight on selecting the right
partner to tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the 
endpoint security space. For insight on selecting the right
partner to tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to