First of all you should read manual. Why? Because you are not see differences between destructors and IDispose. In two words: all you said is about desctructor (objects being destroyed when GC wants), but if you are using using keyword, object will be destroyed just right after the block finished.

Why your approach with Close method calling is wrong? Tell me, what will happen if WriteLine method will throw an exception? Right, you stream will not be closed. But in case of using keyword stream will be closed even if exception thrown. Do you see difference?

Keep your eyes opened.

What using buys you is that the StreamWriter object gets marked for disposal, which I now have to assume means that Close is called at the appropriate time. I agree that “using” is a good approach for many things, but since the Close is the last thing I do in this program I essentially get the same result. In this case, though, since I’m explicitly controlling the Close, I know that the file will be completed immediately. With using, assuming that it will properly complete the file, I have to wait until the GC decides to reclaim the object.

I could wrap the code in a Try-Catch-Finally set, but that would not address the problem I encountered, so I would still want to issue the Close() statement in the finally block.

using(StreamWriter file = File.CreateText(logFileName))
{
foreach (var item in collection)
{
file.WriteLine(“Some Text”);
}
}