August 2nd, 2010 Up ’til now, when I’ve been developing and ClickOnce application, I’ve had to include a UACLauncher as a default option to support any user that is not the administrator on their own machine.
The console app has elevated privileges that are passed on to the re-launched ClickOnce app.
If I didn’t include this, the application would fail with (what I assumed was the first of many permissions errors) a registry access error. I decided to remove the UACLauncher and debug each error as it occurred. All my ClickOnce applications that require registry access to store settings store them in the LocalMachine hive. After googling the registry permission error, the main suggestion that came back was to move the settings to the CurrentUser hive.
Fair enough, but upon publishing the new version, there were no more errors. It seems that the only thing the app was doing that required administrator-level access was to attempt to write to the LocalMachine hive of the registry.
