generic dev sec info (including new dev sec res kit)
http://msdn.microsoft.com/security/
Vista specific dev info (general, index)
http://msdn.microsoft.com/windowsvista/
Vista specific dev sec info
http://msdn.microsoft.com/windowsvista/security/
All of the above do not directly, concisely address what you are
after, i.e. what to do and not do to have a Vista compliant and
deployment friendly application. I am somewhat surprised that
I could not put the finger on the "certified for" 1-2-3 for Vista
applications. (Of course, some is implied by some things, like use
of ClickOnce install, etc.). It is pretty easy to find the logo'd
software requirements/specifications for W2k3 and earlier, but
I am not finding the Vista versions.
Perhaps your best bet is a some reading at the above links, and
also the one below, and also posting to the MSDN forums.
http://msdn.microsoft.com/windowsvis...developerstory
Seriously, try the MSDN forums or if you are a partner that channel
also as I can find now dead links to a draft of the requirements for
Certified for Windows Vista cobranding (3 months old and now gone)
so something should be available (soon).
"Robert Tonsing" <RobertTonsing@discussions.microsoft.com> wrote in message
news:29479242-3DD7-4B16-AEA2-246FD7F31730@microsoft.com...
> Hi,
>
> Is there any documentation on just what operations require administrator
> access? My impression is that some registry keys, some WMI operations etc.
> require admin privileges, but how do we know just which ones? We would
> like
> to change our application to run in user mode normally, and only switch to
> admin mode when really needed.
> --
> Thanks,
> Robert Tonsing