On 27 Sep 2007, at 17:59, Kelly Leahy wrote: > > Oops. Sorry Chris for the duplicate - I forgot to reply to all on > the first one.
Not a problem - I'll put my reply to you below for everyone's benefit. > Here's what I sent to Chris - others, tell me if this won't work, > because I may need this approach myself, later in my installer > building process. > > You could do custom actions that set another property based on its > previous existence... > > consider a property named JVMHOME. Don't initialize (or create) it. > > Write custom actions conditioned on JVMHOME existing, that in > sequence set the JVMHOME to another value if the appropriate > variable is set. > > For instance: > > <CustomAction Id="setJVMpath1" Property="JVMPATH" > Value="[JDKHOME15]" ...>JDKHOME15 AND NOT JVMPATH</CustomAction> > <CustomAction Id="setJVMpath2" Property="JVMPATH" > Value="[JREHOME15]" ...>JREHOME15 AND NOT JVMPATH</CustomAction> > ... > > I think this will work. The ... in the <> are there because I > don't know what other properties you need to make this go into the > proper sequence etc. If you use this approach, please post back > (or reply to me) with the proper complete set of attributes so I'll > know the next time. > > Kelly That looks like a much more promising approach than mine :-) I haven't had to use CustomActions before - do I need to do anything special (apart from putting them inside the <Product>) to make them work? Cheers, Chris ------------------------------------------------------------------------- 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
