I’m adding a new feature to Killink to allow the user to integrate the application with Windows Explorer. Not a difficult task. Just involves making some registry settings. But one registry setting I need to make must go under HKEY_CLASSES_ROOT, and this hive is under administrative control in Vista.
This isn’t such a big deal if I am using an installer. Installers will typically ask for elevated permissions to perform the install. But I’m trying to provide a version that does not require an installer. This means my application will have to ask for elevated permissions when the user clicks the option to integrate with Explorer. It also means I need to display the shield icon indicating that elevated permissions are required to perform the task.
This really has me bummed out because it means more work (and learning). Now I have to learn up to ask for elevated permissions within the application.
Sigh…
Posted in programming. Tagged in killink, windows.
Related Articles
- Retiring My CSV Editor
- Cannot Resolve Machine Name From Mac OS X
- How To Access a Windows 2003 File Share From Mac OS X
- wuauclt svchost and 100% CPU usgage
- When Naming a Configuration File program.exe.config is Bad
- PowerPoint 2007 and Outlook 2003 Don't Play Nice Together
- Delphi (BDS) Live Templates for SQL Server
- Windows Vista to Support 7,000+ New Native APIs
- Native Windows Code Is Here for a While
- MSDN Wiki