I am just learning C# (have been fiddling with it for about 2 days now) and I've decided that, for leaning purposes, I will rebuild an old app I made in VB6 for syncing files (generally across a network).
When I wrote the code in VB 6, it worked approximately like this:
- Create a
Scripting.FileSystemObject
- Create directory objects for the source and destination
- Create file listing objects for the source and destination
- Iterate through the source object, and check to see if it exists in the destination
- if not, create it
- if so, check to see if the source version is newer/larger, and if so, overwrite the other
So far, this is what I have:
private bool syncFiles(string sourcePath, string destPath) {
DirectoryInfo source = new DirectoryInfo(sourcePath);
DirectoryInfo dest = new DirectoryInfo(destPath);
if (!source.Exists) {
LogLine("Source Folder Not Found!");
return false;
}
if (!dest.Exists) {
LogLine("Destination Folder Not Found!");
return false;
}
FileInfo[] sourceFiles = source.GetFiles();
FileInfo[] destFiles = dest.GetFiles();
foreach (FileInfo file in sourceFiles) {
// check exists on file
}
if (optRecursive.Checked) {
foreach (DirectoryInfo subDir in source.GetDirectories()) {
// create-if-not-exists destination subdirectory
syncFiles(sourcePath + subDir.Name, destPath + subDir.Name);
}
}
return true;
}
I have read examples that seem to advocate using the FileInfo or DirectoryInfo objects to do checks with the "Exists" property, but I am specifically looking for a way to search an existing collection/list of files, and not live checks to the file system for each file, since I will be doing so across the network and constantly going back to a multi-thousand-file directory is slow slow slow.
Thanks in Advance.
One little detail, instead of
I would use
Path does reliable, OS independent operations on file- and foldernames.
Also I notice
optRecursive.Checked
popping out of nowhere. As a matter of good design, make that a parameter:And since you mention it may be used for large numbers of files, keep an eye out for .NET 4, it has an IEnumerable replacement for GetFiles() that will let you process this in a streaming fashion.
The
GetFiles()
method will only get you files that does exist. It doesn't make up random files that doesn't exist. So all you have to do is to check if it exists in the other list.Something in the lines of this could work:
Note: You have of course no guarantee that something hasn't changed after you have done the calls to
GetFiles()
. For example, a file could have been deleted or renamed if you try to copy it later.Could perhaps be done nicer somehow by using the
Except
method or something similar. For example something like this:Where the FileNameComparer is implemented like so:
Untested though :p