I've been burned by this to.  All of the conditions for SpawnDialog/NewDialogs 
must be mutually exclusive.  Do no be deceived int thinking that they execute 
in the order specified by @Order.  Have <![CDATA[VALIDUSER = 0]]]> for the 
SpawnDialog and <![CDATA[VALIDUSER != 0]]> For NewDialog.  If your property is 
set to a numeric value, you shouldn't need as "0" etc.

Try this and see what happens.

Regards,
greenaj

---- Michael Clark <mcl...@fullarmor.com> wrote: 
> I have the following UI sequence
> 
>       <Publish Dialog="ServiceInstallDlg" Control="Back" Event="NewDialog" 
> Value="CustomizeDlg">1</Publish>
>       <Publish Dialog="ServiceInstallDlg" Control="Next" Event="DoAction" 
> Value="ValidateUser" Order="1">1</Publish>
>       <Publish Dialog="ServiceInstallDlg" Control="Next" Event="SpawnDialog" 
> Value="InvalidUserDlg" Order="2">VALIDUSER = "0"</Publish>
>       <Publish Dialog="ServiceInstallDlg" Control="Next" Event="NewDialog" 
> Value="MSMQDlg" Order="3">1</Publish>
> 
> 
> I also tried
> 
>       <Publish Dialog="ServiceInstallDlg" Control="Next" Event="SpawnDialog" 
> Value="InvalidUserDlg" Order="2"><![CDATA[VALIDUSER<>"1"]]></Publish>
> 
> 
> In the ValidateUser function I return 1/0 based on if the user name and 
> password are validated, and I want to Display the invalidUser dialog if the 
> value is 0.
> 
> I have validated in the log that the valued is actually changed but it falls 
> through to the MSMQDlg always. Does anyone have any ideas?
> 
> Action start 9:16:09: ValidateUser.
> MSI (c) (0C:BC) [09:16:10:020]: Creating MSIHANDLE (5) of type 790542 for 
> thread 3772
> MSI (c) (0C:BC) [09:16:10:022]: Invoking remote custom action. DLL: 
> C:\Users\mclark\AppData\Local\Temp\MSI5235.tmp, Entrypoint: ValidateUser
> MSI (c) (0C!5C) [09:16:10:127]: Creating MSIHANDLE (6) of type 790531 for 
> thread 3164
> MSI (c) (0C!5C) [09:16:10:128]: Closing MSIHANDLE (6) of type 790531 for 
> thread 3164
> MSI (c) (0C!5C) [09:16:10:176]: Creating MSIHANDLE (7) of type 790531 for 
> thread 3164
> MSI (c) (0C!5C) [09:16:10:178]: Closing MSIHANDLE (7) of type 790531 for 
> thread 3164
> MSI (c) (0C!5C) [09:16:10:320]: Creating MSIHANDLE (8) of type 790531 for 
> thread 3164
> MSI (c) (0C!5C) [09:16:10:327]: Closing MSIHANDLE (8) of type 790531 for 
> thread 3164
> MSI (c) (0C!5C) [09:16:32:499]: PROPERTY CHANGE: Modifying VALIDUSER 
> property. Its current value is '1'. Its new value: '0'.
> MSI (c) (0C:BC) [09:16:32:710]: Closing MSIHANDLE (5) of type 790542 for 
> thread 3772
> Action ended 9:16:32: ValidateUser. Return value 1.
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate 
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
> lucky parental unit.  See the prize list and enter to win: 
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to