I think you're in for some coding. I believe user/local group extensions in http://msiext.codeplex.com support additional nested conditions and can do what you're trying to do, but I haven't checked. It would not be a huge coding exercise to add that to the latter if it's not there. If you want to do more coding, there's also all the code you need except the actual custom action to write an immediate CA to create and remove a user (you can call that in the UI).
I see only one problem with moving creation to the UI, you cannot do silent install any more without supplying the user. If you change the approach, ie. the installer lets you choose a user OR create one in the UI, you get closer to what you want. Another option may be to develop test functionality in the UI about whether the process is going to succeed or fail. I am not sure about password complexity, but there's got to be APIs to do this. Cheers dB. dB. @ dblock.org Moscow|Geneva|Seattle|New York -----Original Message----- From: Tony [mailto:yellowjacketl...@gmail.com] Sent: Tuesday, December 15, 2009 10:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] util:User, util:Group controlling sequencing... 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 ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
