FileSentry is a simple directory watcher. It will traverse a directory recursively, and build an XML
document representing the directory structure. This XML document can be persisted to local storage and
used for later comparison with the directory. Upon comparison, a TreeNodeView control will be populated
and new items checked. This makes it easy to see which files have been added since the last time the XML
I have my media library set up as a Linux Samba share and for some reason FileSystemWatcher events aren't triggered
for these type of drives. I needed something that could quickly show any updates to the directory,
obviously not having
to browse through all the directories.
Using the code
There are two main methods
populateTree. The first method will recurse the given
path and build and XML document like this, and store it in a private variable.
indexDirectories will call
addDirectory which in turn will call
addFile for each item in the
directory if the item is a file, and
addDirectory for each directory item.
private void indexDirectories(string path)
DirectoryInfo dir = new DirectoryInfo(path);
XmlNode node = xmlDoc.CreateElement("directories");
private void addFile(XmlNode xmlParent, DirectoryInfo dir)
foreach(FileInfo theFile in dir.GetFiles("*.*"))
XmlNode filmTitel = xmlDoc.CreateElement("filename");
filmTitel.InnerText = theFile.Name;
After that the
populateTree method is called which takes an XML document as
parameter, against which the recently built XML will be compared and populates the TreeView control.
populateTree method in turn will call
addDirectoryTreeNode to help with the recursive
populating of the TreeNodeView.
private void addDirectoryTreeNode(XmlNode xmlNode, TreeNode parentNode)
foreach(XmlNode xmlSubDir in xmlNode.SelectNodes("directory") )
TreeNode parent = new TreeNode(xmlSubDir.SelectSingleNode("title").InnerText);
foreach(XmlNode xmlSubFile in xmlNode.SelectNodes("filename"))
TreeNode file = new TreeNode(xmlSubFile.InnerText);
The recursive calls are all pretty straight forward, and shouldn't cause any problems.
There are, as you can see, some parameters that are hard-coded which
obviously shouldn't be the case in an "real" application. Bear with
me on these as this is just a demo. Other quirks and peculiarities are all copyright of the author ;).
- Released to codeproject.com on 19 November, 2002.
A seasoned COM/ATL developer, recently being hurled head first into his first .Net project, that loves scuba diving and music.