Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Windos
win32.3rdparty
win32.directx.audio
win32.directx.ddk
win32.directx.graphics
win32.directx.input
win32.directx.managed
win32.directx.misc
win32.directx.networking
win32.directx.sdk
win32.directx.video
win32.dirx.grap.shaders
win32.gdi
win32.international
win32.kernel
win32.messaging
win32.mmedia
win32.networks
win32.ole
win32.rtc
win32.tapi
win32.tapi.beta
win32.tools
win32.ui
win32.wince
win32.wmi
windows.mediacenter
winfx.aero
winfx.announcements
winfx.avalon
winfx.collaboration
winfx.fundamentals
winfx.general
winfx.indigo
winfx.sdk
winfx.winfs
  
 
date: Tue, 27 Nov 2007 09:24:02 -0800,    group: microsoft.public.win32.programmer.tools        back       


question about SHGetFolderPath warnings   
my question is, how seriously do we need to take those SHGetFolderPath 
warnings (about not using approved methods to get folder paths, e.g. Start 
Menu)?  will those warnings prevent us from getting logo certified?

one of the things that our installer does is to check the Start Menu folders 
of all users on the system, not just the current user, in order to perform 
various cleanup tasks.  the way we locate a specific user's folders is to 
load their registry hive and then access 
HKEY_USERS\sid\SOFTWARE\Microsoft\...\Explorer\Shell Folders.

the approved method requires us to use SHGetFolderPath, which means that in 
order to access a specific user's folders we would need an impersonation 
token, which would require us to know the user's password.  this is not 
information that is available to our application, nor should it be.

I've heard of an undocumented system call NtCreateToken, but I don't know 
how to call it and it seems like overkill.

or can we just safely ignore those SHGetFolderPath warnings?

    thanks,
    Mark
date: Tue, 27 Nov 2007 09:24:02 -0800   author:   marko

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us