Don't assume the first person to run your program is an administrator
Источник: BlogsMSDN.com 02.10.2007 18:00
One "optimization" I've seen from some programs is to defer a bunchof system configuration work to the first time the program is runor the first time a feature is requestedinstead of doing it at install time.The problem with this is that the first person to run your programis not guaranteed to be an administrator.
For example, there is one popular media program that doesn'tinstall its CD AutoPlay handler until you run it for the first time.If the first person to run the program is not an administrator,then their AutoPlay handler doesn't get installed and consequentlynever works.
This problem became more acute in Windows Vista,where users do not flex their administrative rights by default,even if they are administrators.Consequently,when run on Windows Vista,this programneverinstalls its AutoPlay handler.
It fell to theapplication compatibility folks to see whatthey could do to rescue this program from the"not compatible with Windows Vista" pile.It's frustrating having to "fix" somethingthat was broken when you got there.
