Cooper gave me another good idea. Microsoft .NET has no decent File class. By decent, I mean a class that represents a file, with a name , and a path , that can be used to open , close, rename, delete, and so on. Instead, there is this all-powerful Directory class that can do those things. The implication , however, is that when you want to do anything with files, you have nothing to work with but a collection of strings representing the names of the files. String, of course, has no methods that are anything to do with files.
Cooper suggests building a class to support the kinds of things we need to do with files. Because this Directory to String thing has irritated me for quite a while, Im thinking its a good idea.