Skip to Content
C# 3.0 Cookbook, 3rd Edition
book

C# 3.0 Cookbook, 3rd Edition

by Jay Hilyard, Stephen Teilhet
December 2007
Intermediate to advanced
896 pages
19h 57m
English
O'Reilly Media, Inc.
Content preview from C# 3.0 Cookbook, 3rd Edition

3.16. Assuring an Object's Disposal

Problem

You require a way to always have something happen when an object's work is done or it goes out of scope.

Solution

Use the using statement:

	    using System;
	    using System.IO;

	    // ...

	    using(FileStream FS = new FileStream("Test.txt", FileMode.Create))
	    {
	        FS.WriteByte((byte)1);
	        FS.WriteByte((byte)2);
	        FS.WriteByte((byte)3);

	        using(StreamWriter SW = new StreamWriter(FS))
	        {
	            SW.WriteLine("some text.");
	        }
	    }

Discussion

The using statement is very easy to use and saves you the hassle of writing extra code. If the Solution had not used the using statement, it would look like this:

	    FileStream FS = new FileStream("Test.txt", FileMode.Create);
	    try
	    {
	        FS.WriteByte((byte)1);
	        FS.WriteByte((byte)2);
	        FS.WriteByte((byte)3);

	        StreamWriter SW = new StreamWriter(FS);

	        try
	        {
	           SW.WriteLine("some text.");
	        }
	        finally
	        {
	            if (SW != null)
	            {
	                ((IDisposable)SW).Dispose( );
	            }
	        }
	    }
	    finally
	    {
	       if (FS != null)
	       {
	           ((IDisposable)FS).Dispose( );
	       }
	    }

Several points to note about the using statement:

  • There is a using directive, such as:

    	using System.IO;

    which should be differentiated from the using statement. This is potentially confusing to developers first getting into this language.

  • The variable(s) defined in the using statement clause must all be of the same type, and they must have an initializer. However, you are allowed multiple using statements in front of a single code block, so this isn't a significant restriction.

  • Any variables defined in the using clause are considered read-only in the body ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

AirBnbBlueOriginElectronic ArtsHomeDepotNasdaqRakutenTata Consultancy Services

QuotationMarkO’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
Julian F.
Head of Cybersecurity
QuotationMarkI wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
Addison B.
Field Engineer
QuotationMarkI’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
Amir M.
Data Platform Tech Lead
QuotationMarkI'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Mark W.
Embedded Software Engineer

You might also like

C# 6.0 Cookbook, 4th Edition

C# 6.0 Cookbook, 4th Edition

Stephen Teilhet, Jay Hilyard
C# Cookbook

C# Cookbook

Stephen Teilhet, Jay Hilyard
C# Cookbook

C# Cookbook

Joe Mayo
C# Cookbook, 2nd Edition

C# Cookbook, 2nd Edition

Jay Hilyard, Stephen Teilhet

Publisher Resources

ISBN: 9780596516109Errata Page