Quote Originally Posted by sytto
I recently explored this decision, in the end I'm going with Filesystem object.

Posters here are what got me to look into the .net way and although it seems more robust i still feel i have more control over what i'm trying to accomplish with my file then i do with the .net method.

Maybe a future project i'll use the .net way but at the moment i'm sticking with old tried and true way. My familiarity may have allot to do with my decision but at the end of the day i can't help feel that i'm much more in control over my data.

my 2 cents.
You can do anything you want with any file down to the byte using .NET file I/O. There is no advantage to using unmanaged code for I/O.

The classes in the Stsrem.IO namespace are what you should be looking at first. There is also the My.Computer.FileSystem object. Many of the methods of the My.Computer.FileSystem object wrap members of classes in the System.IO namespace. For instance, My.Computer.FileSystem.FileExists calls IO.File.Exists and My.Computer.FileSystem.RenameFile calls IO.File.Move. Many others use the Windows Shell, allowing you to display the same progress dialogues used by Windows Explorer.