Couple more questions... What if we want the user created on install, removed during uninstall, but NOT removed during the "uninstall" that occurs during major upgrade? Do we create two components with a <util:User> component one with RemoveOnUninstall="yes" and the other with RemoveOnUninstall="no" and use a condition (where?) to select the correct component during the correct scenario?
The add user to group mechanism seems fine, but the issue I see with the create user function being performed as a deferred action is that the end user feed back is horrible. What if we are given an invalid name, Password complexity, etc. All the user gets to see is a "error creating user account -2234234342". And rollback starts. Whereas if we were to create the user during the UI sequence, we can show the user the crazy error and dump them back on the account dialog asking them to verify the information they provided. This isn't as much of an issue for the group membership function as we can only add the user to existing groups. So, a simple type-o won't fail the install. On Mon, Dec 14, 2009 at 4:11 PM, Blair <os...@live.com> wrote: > None of those actions should ever occur during the UI sequence. The UI > sequence is intended exclusively for gathering information from the user to > guide the installation. -- Tony ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
