1. Give More Feedback

Here you go:. Put the following words into a text file called ftp.scr: Your ftp user account name Your ftp password dir quit.

Execute this command: ftp -s:ftp.scr ftp.sitename.com ftp.txt. Write a script to process the contents of ftp.txt in order to determine the names of the files and folders on the ftp site. Generate a new script file, similar to the one in Step 1, to download the files. Ditto to process the folders. The above instructions apply to the native Windows ftp.exe command, which is very basic. It is likely that you can find more intelligent versions of an ftp command line tool that would save you most of the above steps. Here you go:.

Put the following words into a text file called ftp.scr: Your ftp user account name Your ftp password dir quit. Execute this command: ftp -s:ftp.scr ftp.sitename.com ftp.txt.

Write a script to process the contents of ftp.txt in order to determine the names of the files and folders on the ftp site. Generate a new script file, similar to the one in Step 1, to download the files. Ditto to process the folders. The above instructions apply to the native Windows ftp.exe command, which is very basic. It is likely that you can find more intelligent versions of an ftp command line tool that would save you most of the above steps. Hi Oberwald In the method you hav mentioned the file ftp.txt contains the out of all ftp commands executed. The dir commands.

It will be something like this dir 200 PORT command successful. 125 Data connection already open; Transfer starting. 03-25-13 12:01AM 87 Bs.txt 03-25-13 12:01AM 51 Co.txt 03-23-13 01:22PM newfile 226 Transfer complete. Ftp: 162 bytes received in 0.00Seconds 162000.00Kbytes/sec.

Get program path in VB.NET? Full.exe path, including the program.exe name on the end. How to send a file via FTP that is in the same folder as my program? Background I need to pull the file locations (path and filename). Locations (path and filename) for all files at a. Get the file names from the FTP.

Ftp But how to process this file to copy files and folders?I think it needs lot of effort!!

In my VB.NET 2.0 application, I'm using Directory.GetFiles to get the files from a drive of other peoples PC's. I am recursivly navitaging subfolders, and for each folder, calling the GetFiles function. On one or more folders, I am geting an exception from GetFiles, 'Illegal Charcters inPath'. When this exception is thrown, the string array of filenames that GetFiles returns is nothing. So, GetFiles is apparently all or nothing.

Is there anyway to at least get the files that would not throw an exception, in the case where a folder has more than one file but only one file contains illegal characters in the path. Any alternative is viable, in that this is a forensics applicaiton, and I really need, at least, all the file names, and a FileInfo object of any file that would not throw an exception. I'm open to correction on this but, so far as I know, that error refers to the PATH on which you are calling.GetFiles, not to any FILES found on that path.

So it is bound to be 'all or nothing' so far as any particular PATH is concerned. So what you are encountering, in your recursion, is a Directory/Folder name which contains invalid characters. And.GetFiles won't work on that Directory/Folder: hence the empty array. If it works on the Directory/Folder, I think (although I haven't tested this) it will return an array including even filenames that may have invalid characters. To answer all outstanding questions: I am positive the culprit is the filename, not the directory name. I've verified this three ways. 1) First, I can use Windows Explorer to navigate thru the folder structure down to the files which cause GetFiles to throw the exception.

2) The file(s) that cause GetFIles to throw the exception have an ASCII Char(15) as the first character in the filename. These are Microsoft Word Documents.

How the illegal character got into the file name, I have not idea. Remeber this is a forensics tool to examine others PC's. 3) I can remove the files containing the illegal characters from the folder (leaving 1 file), and GetFiles does not fail. 4) Calling GetDirectories on the parent directory does not fail, which further supports my statement that the directory/folder is not the culprit. This is difficult for me to test, as I do not appear to have any filenames on my own system with invalid characters in them;-) But I'll take your word for it that an invalid file name causes an error with respect to the whole directory/folder even though the docs expressly state it to be an error generated by the path Visual Basic (Declaration) Public Shared Function GetFiles ( path As String ) As String. ArgumentException path is a zero-length string, contains only white space, or contains one or more invalid characters as defined by InvalidPathChars.

Yes, I've tried DirectoryInfo.GetFiles. Same error message. I believe my test is correct, but let me state it again to see if someone else agrees or disagrees with how I determined the path name passed to the GetFiles function is not the culprit.

First, I rename the folder which contains the suspect files. I run my test program again, and get the same 'illegal characters in path' error. Next, I delete the suspect files from the folder, leaving files without bad filenames. I run my test program again, and it runs through completion. Sure seems to me that the suspect files are causing the problem. In order for you to test properly, you'd need files with invalid characters in the filename.

Give More Feedback

I've tried every conceivable option I could think of to create such a file, but Windows will not let it happen. I'd send someone this file to test, if someone was so inclined. 'I've tried every conceivable option I could think of to create such a file, but Windows will not let it happen.' So did I before my last post. And, since then, I've also tried renaming files in DOS to include invalid characters - similarly without success. Not being able to test means I can't really help.

I rather fear that the process of transferring files with illegal characters in their names will either fail, or will change the filenames, but we can give it a try. Go here log on and try to upload a bad file or two and a good file or two (as 'controls'). If they'll zip up, that would be best. If you're successful, post the URL that you're given back here.

And, although your description of how you've reached your conclusion that it is the filename rather than the path look sound enough to me, the devil can be in the detail. So if you'd like to post the crucial bit of your code (I'm particularly interested in how you handle the recursion) - either here or as part of any successful upload - that would be useful, too. Finally, when you tested with APIs, you said 'such as GetFirstFile, GetNextFile'.

I think (but again I'm open to correction) that those are 'enhancements' of the basic APIs FindFirstFile, FindNextFile. Did you try the latter? It's as I feared. The Zip archive shows the file name as including an unreproducable character and - presumably for that reason - will neither allow me to View the file or, by double-clicking on it, to open it with MSWord.

But, when I Unzip it, that character has gone. It has now become a valid file name so everything works OK. Can please you try again, just uploading the file as it is? In the meantime, I'll see if I can spot anything just by studying the code - although my first impression is that it's not doing anything that would, of itself, cause a problem like this. I am, by the way, in the UK, and shortly off to bed. So you may not hear any more from me for a few hours.

I cannot see any way - other than, as you concluded, the 'all or nothing' error in Directory.GetFiles(pPath) being generated by a single bad file name among the files to be 'got' - in which your code would behave in the way you describe. Just reading code is no proper substitute for testing it but, until I get a bad filename to work with and that proves us both wrong, I agree with your diagnosis. One apparent oddity I did spot: although nothing to do with this problem. On line 5 you declare FileExtDS.

Within the For Each. Next block running from lines 24 to 114 you use it on various lines - e.g. But at line 111 you.Dispose of it. What happens if lines such as 47, etc, are encountered in a second or subsequent run through the For Each. Or could that just never occur?

I'll wait to see if there's any more luck with transferring an example file unzipped. Michael Unless you have access to another site to which you can upload and from which I can download a file, I'm afraid I'm stumped, too. I've made it a rule since I joined EE not to deal direct with anyone by e-mail, so that approach is out. And even if you can organise an upload/download, it wouldn't surprise me if it hits further problems on rejecting, or changing, 'illegal' file names. But I wonder whether you are ever going to do this in.NET? At least without other preliminaries.

The illegal characters are obviously being stored in the file system and, I gather from your description, getting as far as Windows Explorer. But then any Windows or.NET approach seems to hit the blockage that - for any processing at all (e.g. Programmatically reading the filename or changing it) - an illegal character check is imposed by the system and fails (or the illegality is 'corrected', as in my unzipping the files).

This suggests to me that you might need to be digging into the file system with direct disk reads. It's years since I did any of that.

Not only am I very rusty but also things have changed so much that I wouldn't now know where to start. So I wonder whether you might do better to ask another question - not concerned with.NET methods such as.GetFiles or even Windows APIs, but specifically with reading file name info direct from disk - in a more appropriate zone.

If you can get a list of filenames - 'illegal' as well as legal that are actually there, then it should be possible to 'code round' the illegal ones in.NET: though it would be a much slower and more tedious operation than if.GetFiles (or some equivalent) could be made to work. I'll leave the ball in your court.

If you want to persist in trying to get a test file or two to me I'll see what, if anything, I can suggest as a workaround within the limitations of.NET (and my own knowedge/skill). But if you want to ask elsewhere, and delete this question and get a refund of points, I shan't object.