C# FileStream Handling

[sudhivns]

Hi,

using (FileStream fs = File.Create(path))
{
                Byte[] info = new UTF8Encoding(true).GetBytes("Text");
                // Add some information to the file.
                fs.Write(info, 0, info.Length);
                fs.Close(); // Is it mandaroty to call Close on stream
}

My understanding is that in above piece of code, no need to fs.Close() since it will be handled when the scope of using block finishes.
Whether it is corret.

[CyberSoftHari]

That is closing the block not the file stream. You have to use it mandaroty.

[r035198x]

Hi,

using (FileStream fs = File.Create(path))
{
                Byte[] info = new UTF8Encoding(true).GetBytes("Text");
                // Add some information to the file.
                fs.Write(info, 0, info.Length);
                fs.Close(); // Is it mandaroty to call Close on stream
}

My understanding is that in above piece of code, no need to fs.Close() since it will be handled when the scope of using block finishes.
Whether it is corret.

That using decomposes to code with a try/finally thing with IDisposable.Dispose() called in the finally part.
If Microsoft have implemented IDisposable correctly for FileStream (I think they have) then thre's no need for that Close there.

[Plater]

I would recomend calling .Close() regardless, it's good practice.
Also pay attention to the tooltip on the .Close() method, filestream says it closes the filehandle and stream, BUT some of the other stream objects do NOT close underlying streams when you call .Close(), so it creates memory leaks.

[r035198x]

Like I said, "using" calls Dispose() which is "stronger" (in terms of clean up) than Close(). Putting Close inside the using block is just redundant and shows lack of understanding of the using block itself while defeating the purpose of using it.