FileInfo can't use in using

[tshad]

Can't use FileInfo in using statement?

I have the following statement:

using (FileInfo fInfo = new FileInfo(fromIm agePath + "\\" +
(string)dr["originalFileNa me"]))

and I get the following error:

'System.IO.File Info': type used in a using statement must be
implicitly convertible to 'System.IDispos able'

I assume that this means I can't use it in my using statement.

So does this would mean that I need to explicitly close fInfo object:

fInfo.Close()

Or should I just let the garbage collector handle it?

Thanks,

Tom

[Jon Skeet [C# MVP]]

tshad <ts***@dslextre me.comwrote:

Can't use FileInfo in using statement?

No, because it doesn't implement IDisposable.

So does this would mean that I need to explicitly close fInfo object:

fInfo.Close()

Do you see a Close method defined anywhere on FileInfo? What would you
expect it to do?

Or should I just let the garbage collector handle it?

Yes. There are no unmanaged resource to release.

--
Jon Skeet - <sk***@pobox.co m>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[tshad]

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...

tshad <ts***@dslextre me.comwrote:

>Can't use FileInfo in using statement?

No, because it doesn't implement IDisposable.

>So does this would mean that I need to explicitly close fInfo object:

fInfo.Close()

Do you see a Close method defined anywhere on FileInfo? What would you
expect it to do?

>Or should I just let the garbage collector handle it?

Yes. There are no unmanaged resource to release.

How would you know when to close the object?

Doesn't FileInfo create an object and therefore resources?

Then why doesn't it need to be closed - yet FileStreams need to be closed?

Thanks,

Tom

--
Jon Skeet - <sk***@pobox.co m>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Jon Skeet [C# MVP]]

tshad <ts***@dslextre me.comwrote:

Yes. There are no unmanaged resource to release.

How would you know when to close the object?

When there are unmanaged resources involved, such as open files.

Doesn't FileInfo create an object and therefore resources?

No. FileInfo reads file system information when it needs to, but it
doesn't hold any unmanaged resources open.

Then why doesn't it need to be closed - yet FileStreams need to be closed?

While a FileStream is open, it has an OS handle to the open file.
That's an unmanaged resource.

--
Jon Skeet - <sk***@pobox.co m>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[tshad]

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...

tshad <ts***@dslextre me.comwrote:

Yes. There are no unmanaged resource to release.

How would you know when to close the object?

When there are unmanaged resources involved, such as open files.

>Doesn't FileInfo create an object and therefore resources?

No. FileInfo reads file system information when it needs to, but it
doesn't hold any unmanaged resources open.

>Then why doesn't it need to be closed - yet FileStreams need to be
closed?

While a FileStream is open, it has an OS handle to the open file.
That's an unmanaged resource.

So the object "fInfo" in

using (FileInfo fInfo = new FileInfo(fromIm agePath + "\\" +
(string)dr["originalFileNa me"]))

is just an object and will be disposed of by the garbage collector after the
method is exited or goes out of scope?

Thanks,

Tom

>
--
Jon Skeet - <sk***@pobox.co m>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Peter Duniho]

On Sun, 01 Jun 2008 00:18:51 -0700, tshad <ts***@dslextre me.comwrote:

So the object "fInfo" in

using (FileInfo fInfo = new FileInfo(fromIm agePath + "\\" +
(string)dr["originalFileNa me"]))

is just an object and will be disposed of by the garbage collector after
the
method is exited or goes out of scope?

It will be collected (I prefer that term over "disposed" since the latter
has a specific meaning in .NET) according to the standard garbage
collector rule: when it is no longer reachable.

Depending on how you use the instance, this may well be when the variable
goes out of scope (exiting scope within the method, or the method itself,
for example).

Also keep in mind that it's not just FileInfo that's being collected. It
may contain other things that are also unreachable when the FileInfo
instance becomes unreachable and those will be collected as well. That's
just how the garbage collection works. The beauty of it is that you don't
need to worry about it.

The "dispose" paradigm exists in .NET primarily because of unmanaged
resources, and if an object doesn't implement IDisposable, then you don't
need to dispose it (and can't :) ).

Pete

[Jon Skeet [C# MVP]]

tshad <ts***@dslextre me.comwrote:

While a FileStream is open, it has an OS handle to the open file.
That's an unmanaged resource.

So the object "fInfo" in

using (FileInfo fInfo = new FileInfo(fromIm agePath + "\\" +
(string)dr["originalFileNa me"]))

is just an object and will be disposed of by the garbage collector after the
method is exited or goes out of scope?

It's just an object, and it will be garbage collected *at some point*
after it is used for the last time. That might be before the method
finishes (the garbage collector can be quite aggressive in determining
when something has been used for the last time) or a lot later (if the
garbage collector happens not to run for a while).

--
Jon Skeet - <sk***@pobox.co m>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com