8 replies to this topic

[CM XS]

the documentation i've read (i've just started with WI), seems to say that the sequence my WI install should follow is
1) get user input with UI
2) run custom actions
3) install files

what i'm wondering is if it's possible to run a standard or custom action while in the middle of the UI flow.  for example, if the data entered by the user into a UI dialog needs validation, then I'd like to run an action to validate the data before the next dialog is shown, so that if there's a problem with the data, the user is warned and returned to the same data-entry dialog.

is this possible?  does this go against recommended practices?  

we're currently using only ORCA and VB/VC++ for  setup authoring.

thank you
CM

[CM XS]

forget it, found the answer.

[Stefan Krueger]

That's perfectly okay. You shouldn't use custom actions that modify the target system in the user interface sequence, but you can use custom actions to validate user input, set properties or paths, select features etc.

[CM XS]

thank you for the clarification

[ConfigControl]

How did you validate the user input using a CA?

[Stefan Krueger]

The content of the edit field is stored in a property. You can use a dll to verify this string.

[kc]

How do i push the original dialog box back to the user to correct the edit box. I designed a dialog called MyDialog and call it using MsiDoAction(hMSI, "MyDialog"); But the dialog dint appears. Pls help. Thanks

KC

[kc]

How do i push the original dialog box back to the user to correct the edit box. I designed a dialog called MyDialog and call it using MsiDoAction(hMSI, "MyDialog"); But the dialog dint appears. Pls help. Thanks

KC