' This query determines whether the two folders contain ' Create the FileCompare object we'll use in each query ' on a local drive and add files to them.ĭim dir1 As New System.IO.DirectoryInfo(pathA)ĭim dir2 As New System.IO.DirectoryInfo(pathB)ĭim list1 = dir1.GetFiles('*.*', System.IO.SearchOption.AllDirectories)ĭim list2 = dir2.GetFiles('*.*', System.IO.SearchOption.AllDirectories) ' Create two identical or different temporary folders In a real-world scenario, you should modify this comparer to perform a more rigorous equality check.

It just uses the name and length in bytes of each file to determine whether the contents of each folder are identical or not. The class is not intended for use in real-world scenarios. The FileComparer class shown here demonstrates how to use a custom comparer class together with the Standard Query Operators. It would make a lot more sense to replace that one tool with one that understands folders than to build a Rube Goldberg machine to auto-sync folders into a flat list.The techniques shown here can be adapted to compare sequences of objects of any type.

With this and your other thread (which are both really the same question, I think?), it seems like you are layering on more and more tools and complexity in an attempt to work around a fairly ridiculous limitation of the 'database' tool you are using. Synching the copies is the same job as synching the originals, and that's the part that's problematic. What would adding a TeraCopy copy-and-verify to an intermediate folder get you, other than more complexity? You'd just be duplicating your source folders and then synching the duplicate to your destination, which doesn't seem to get you anywhere. There's no underlying 'basic compare command', it's just the way people want synching to work in almost all cases, and the only way synching can work in the general case (where two files may have the same names in different directories and thus cannot be resolved to a single flat destination).

Compare contents of two folders