Flush() and Close()

[guy]

I can't find this in the documentation so I'm asking it here:

I assume that if I call Close() on a Stream based class that Flush() does
not need to be called before as it is implicitly called by Close()?

Thanks

[Chris Ballard]

That is correct.

When you close the stream any remaining buffered content is written out at
that point, otherwise that data would be lost.

Chris.

"guy" wrote:

I can't find this in the documentation so I'm asking it here:

I assume that if I call Close() on a Stream based class that Flush() does
not need to be called before as it is implicitly called by Close()?

Thanks

[Jon Skeet [C# MVP]]

guy <wi*********@ho tmail.com> wrote:

I can't find this in the documentation so I'm asking it here:

I assume that if I call Close() on a Stream based class that Flush() does
not need to be called before as it is implicitly called by Close()?

Yup.

For most streams (CryptoStream excepted due to a bug) you can just call
Dispose instead, which is much easier with a using statement:

using (Stream x = ...)
{
....
} // Dispose called automatically here

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Champika Nirosh]

Hi guy,

Calling System.IO.Strea m.Close on a Stream flushes any buffered data,
essentially calling System.IO.Strea m.Flush for you. System.IO.Strea m.Close
also releases operating system resources such as file handles, network
connections, or memory used for any internal buffering.

Nirosh.
"guy" <wi*********@ho tmail.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

I can't find this in the documentation so I'm asking it here:

I assume that if I call Close() on a Stream based class that Flush() does
not need to be called before as it is implicitly called by Close()?

Thanks