File & FileInfo

  • Thread starter Thread starter rn5a
  • Start date Start date
R

rn5a

To work with files, when should one use the File class & when should
one use the FileInfo class?

Similarly, to work with directories, when should one use the Directory
class & when should one use the DirectoryInfo class?
 
Hi,

To work with files, when should one use the File class & when should
one use the FileInfo class?
Click to expand...

The File class is static, you cannot instantiate a File, only a
FileInfo. So if you need to use methods without having an instance to
worry about, the File class is good. However, most of the time, I prefer
to use FileInfo, create an instance and keep it for later, when I need
to use it for other purposes. That's exactly the same for Directory
(static) and DirectoryInfo.
Similarly, to work with directories, when should one use the Directory
class & when should one use the DirectoryInfo class?
Click to expand...

HTH,
Laurent
 
Many many thanks, Laurent, for highlighting the differences.

You have said that most of the times, you prefer using the FileInfo
object, creating an instance of it & keeping it for later use when you
need to use it for other purposes but doesn't that mean unnecessarily
consuming more server resources in the meantime?

By "in the meantime", I mean that suppose you instantiate the FileInfo
object on the second line of a sub-routine & use it, say, on the fifth
line of the same sub-routine. After that, you do not use this instance,
say, till the 70th line of the sub-routine. This means that all the
code between the 6th & the 69th line gets executed before you use this
instance of the FileInfo object again on the 70th line of the
sub-routine. Why keep the object in the server memory while the code
between the 6th & the 69th line is being executed? Why not just use the
File object twice as & when required?

Please correct me if I am wrong.

BTW, apart from the difference which you have talked about, are there
any other differences between File & FileInfo and Directory &
DirectoryInfo?

Hi,

To work with files, when should one use the File class & when should
one use the FileInfo class?
Click to expand...

The File class is static, you cannot instantiate a File, only a
FileInfo. So if you need to use methods without having an instance to
worry about, the File class is good. However, most of the time, I prefer
to use FileInfo, create an instance and keep it for later, when I need
to use it for other purposes. That's exactly the same for Directory
(static) and DirectoryInfo.
Similarly, to work with directories, when should one use the Directory
class & when should one use the DirectoryInfo class?
Click to expand...

HTH,
Laurent
--
Laurent Bugnion [MVP ASP.NET]
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch
Click to expand...
 
Hi,

Many many thanks, Laurent, for highlighting the differences.

You have said that most of the times, you prefer using the FileInfo
object, creating an instance of it & keeping it for later use when you
need to use it for other purposes but doesn't that mean unnecessarily
consuming more server resources in the meantime?
Click to expand...

Yes. I shouldn't have said "most of the time", rather "often". What I
meant is that I often started by using the File method, and suddenly
realized "Oh, I will need that file later for another use" and then
refactoring in order to use a FileInfo instead.

My intent was only to say that though the File class can do a lot, it
cannot replace the FileInfo class completely.

By "in the meantime", I mean that suppose you instantiate the FileInfo
object on the second line of a sub-routine & use it, say, on the fifth
line of the same sub-routine. After that, you do not use this instance,
say, till the 70th line of the sub-routine. This means that all the
code between the 6th & the 69th line gets executed before you use this
instance of the FileInfo object again on the 70th line of the
sub-routine. Why keep the object in the server memory while the code
between the 6th & the 69th line is being executed? Why not just use the
File object twice as & when required?
Click to expand...

You know, object oriented design is not saving resources, rather in the
contrary. However, it makes code easier to refactor, modify, maintain,
extend, etc... It also makes it easier to understand. Using static
classes or methods, you can program C# almost "procedurally" (inventing
words here, I think). That doesn't mean that you should do it always.

However, I don't want to push you to use FileInfo all the time (and I
also don't use it always!!), I just wanted to moderate your opinion
which seemed to be partial to the File class and put forward the
advantages of the FileInfo class.
Please correct me if I am wrong.
Click to expand...

I don't think you're wrong and I don't think I am right. It really
depends on the scenario ;-)

BTW, apart from the difference which you have talked about, are there
any other differences between File & FileInfo and Directory &
DirectoryInfo?
Click to expand...

I think your best bet here is to check the MSDN documentation and
compare which methods each class offers:

http://msdn2.microsoft.com/en-us/library/system.io.fileinfo.aspx
http://msdn2.microsoft.com/en-us/library/system.io.file.aspx
http://msdn2.microsoft.com/en-us/library/system.io.directoryinfo.aspx
http://msdn2.microsoft.com/en-us/library/system.io.directory.aspx

Greetings!
Laurent
 
Back
Top