Can't access digital camera to copy from in code

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to copy pictures from a digital camera in code. When I use the
FolderBrowserDialog, it won't let me select the camera as the folder. I have
gotten around this by using Shell32.BrowseForFolder. I am then also able to
get the names of the files. However, the path is a pidl (i believe). So I am
unable to utilize .Net IO classes to manipulate the files. This is windows
form that ultimately will allow the user to browse for a camera, pick a
client, then ftp pictures to the server for later processing.
Thanks, Glen
 
Hi Glen,

We have reviewed this issue and are currently researching on it. We will
update you ASAP. Thanks for your patience!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Hi Glen,
I noticed you get a pidl from BrowseForFolder. At this situation we can
call SHGetPathFromIDList to get the system path. Then you should be able to
utilize .Net IO classes to manipulate the files.

Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
 
Rhett,
When I look at the path on a FolderItem, this is what it is
@";;{E211B736-43FD-11D1-9EFB-0000F8757FCD}\devid:{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0000:\0000\Root\000_0091"
I remove the ;; and apend .jpg and send the string to FileExists();
I get a false returned. The good thing is FileExists doesn't throw an
Exception - it just can't find the file.
Ideas?
 
Hi Glen,
Have you tried SHGetPathFromIDList? It should convert the pidl to a normal
folder path (eg. g:\image)? Then you should be able to control the files as
usual with net io.
PS: please don't change the pidl directly. shell provides a function named
SHParseDisplayName which is a better way to change a normal folder/file
path to pidl.


Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
 
Back
Top