C# using Statement: Dispose and IDisposable

Understand the using statement. Handle IDisposable types like StreamReader with using.

Using. The using block helps manage resources. It protects the whole system's resources by specifying the scope of the usage of the resource.

The using statement is combined with a type that implements IDisposable. Things like StreamReader or StreamWriter implement IDisposable.StreamReaderStreamWriterInterface

To begin, this program defines a class called SystemResource. The class implements the IDisposable interface and the required Dispose method.
Note: In the Main method, we wrap the SystemResource instance inside a using statement.
On execution: First the SystemResource instance is allocated upon the managed heap. Next the "1" is written.
And: The "0" is written because the Dispose method is invoked. And finally, the "2" is printed.
Info: As demonstrated, the Dispose method is called immediately when control flow exits the using block.
C# program that uses using statement using System; using System.Text; class Program { static void Main() { // Use using statement with class that implements Dispose. using (SystemResource resource = new SystemResource()) { Console.WriteLine(1); } Console.WriteLine(2); } } class SystemResource : IDisposable { public void Dispose() { // The implementation of this method not described here. // ... For now, just report the call. Console.WriteLine(0); } } Output 1 0 2

Example 2. It is possible to nest multiple using statements one after another. You do not need to use any curly brackets in this case.
Tip: In the second or further using statements, you can use the variables declared in previous using statements as well.
C# program that nests using blocks using System; class Program { static void Main() { using (SystemResource resource1 = new SystemResource()) using (SystemResource resource2 = new SystemResource()) { Console.WriteLine(1); } } } class SystemResource : IDisposable { public void Dispose() { Console.WriteLine(0); } }

Notes, performance. If we omit "using" or Dispose calls, we may improve performance—until the code stops working. So it is best to add "using" when it is supported.

Discussion. It is most common to use "using" with types already defined in the .NET Framework. Some of these types include BinaryReader, BinaryWriter, DataTable.BinaryReaderBinaryWriterDataTable
Info: Use a resource acquisition expression inside the using statement. You do not need to implement any interfaces.

Summary. The using statement invokes the Dispose method found in the IDisposable interface implementation. This article does not describe a useful implementation of Dispose.

Review, Dispose. The using statement interacts with Dispose. It affects the path of the control flow in the virtual execution engine.

© 2007-2020 Sam Allen. Every person is special and unique. Send bug reports to info@dotnetperls.com.