Jeremy Lew wrote: > I hear you, but it doesn't look like I have much choice. If the service > fails to start, I need to either instruct the user to start it from the > control panel, or force a reboot. Both of those options are pretty icky > as well. >
First, I doubt it'll work: MSI runs as a service, which doesn't have free reign to show UI. I doubt you'll be able to get a UAC prompt from the execute sequence, though it would probably work if you run it from the tail end of the UI sequence. Second, there are other options: 1. If it's a .NET service installed to the GAC, don't. There's almost no benefit to the GAC for an auto-start service, as it's not restarted (often) and is cold-starting the CLR. 2. If it's appropriate, change the ACLs (using <Permission>) to let users control the service. Then you can do it after InstallFinalize. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
