We currently have an MSI that is created with WiX 3.5. The application is in .NET 3.5. We generate a bootstrapper using the boostrapper task in an MSBuild file. It’s pointing at the 6.0a SDK files.
When users have UAC on and they install, they have to right-click the setup.exe and select run-as administrator.
What I would really like is to have the setup.exe automatically prompt to elevate (using that yellow dialog I see in other installs).
Better yet, I’d like the MSI to do this and do away with the setup.exe completely, but I think that is what WiX 3.6 is about, right?
If I create the boostrapper using ApplicationRequiresElevation="true" this requries the 7.0a SDK, correct? Will the bootstrapper then prompt to elevate automatically? Does this mean the application has to be a .NET 4 application? I wouldn’t think so…
We’ve used WiX 3.0 and were able to elevate privileges. However, we didn’t elevate our bootstrapper. We elevated the MSI file itself, through the Package property:
As a side note, our bootstrapper is signed (using signtool.exe from the v6.0A SDK) with our official certificate. I’m not sure if this causes the bootstrapper to also require elevated privileges.
UPDATE:
We’ve got an app.manifest file on our setup.exe bootstrapper project that requires the executable to be run at the administrator level. See the sample below: