What does Using(.....){...} mean

Question

Possible Duplicates:
Using the using statment in c#
What is the C# Using block and why should I use it?

Just wondering what this means? I've seen lots of tutorials online that have the syntax:

using (SqlCeCommand cmd2 = new SqlCeCommand("SELECT city FROM cities JOIN states ON states.id=cities.state WHERE states.state='" + read.GetString(0) + "'", con))
{
  SqlCeDataReader readCities = cmd2.ExecuteReader();
  while (readCities.Read())
  {
    parent.Nodes.Add(readCities.GetString(0));
  }
}

Why is it used? I tried searching Google, but it comes up with the 'using' keyword which is used for including dll's and other files.

Answer 1

The using just instructs the compiler to write code that will call the Dispose method on the variable you're using. Only types that implement 'IDisposable' can be used with using statements.

In your example, cmd2 will be disposed when the code in the {} finishes.

Answer 2

"Defines a scope, outside of which an object or objects will be disposed"
See using statement

Answer 3

using is applied to objects that implement IDisposable. It ensures that, when leaving the using block (whether normally, or via an exception, or whatever), the disposable object's Dispose method is called.

Answer 4

The using statement

using(var your_object = new object_that_implements_IDisposable()) { ... }

is syntactic sugar for the following:

var your_object = new object_that_implements_IDisposable()
try
{
    ...
}
finally
{
    ((IDisposable)your_object).Dispose();
}

This is only applicable for classes that implement IDisposable. It is helpful for cleaning up code where you have objects that take, for example, system resources (file handles, database connections, sockets, etc.) that need to be cleaned up after you are done to free the resource for the rest of the system.

In theory, you could leave out the .Dispose() call, but then you would have to wait for the Garbage Collector to free the kept resources. The GC is awesome at knowing when to free objects to reclaim their memory usage, but it has no idea that it needs to free objects to have them give up other system resources. Thus, these critical resources might not be given up until after the GC decides it needs the memory used by the owner. Thus, you definitely want to dispose of your objects when you are done with them (if they are disposable)!

As to why you'd use using over try/finally, it is purely a coder's preference. I prefer using because you can cascade them:

using(var a = new class())
using(var b = new class())
using(var c = new class())
using(var d = new class())
{
    ...
}

You'd need quite a few more lines of code to do that with try/finally.

See also:

• http://stackoverflow.com/questions/614959/using-the-using-statment-in-c
• http://stackoverflow.com/questions/212198/what-is-the-c-using-block-and-why-should-i-use-it
• http://msdn.microsoft.com/en-us/library/yh598w02%28VS.80%29.aspx

Answer 5

Using statement is defines a scope, that outside of it the object or objects will be disposed.

Answer 6

Using is a cool way of cleaning up resources, it is equivalent to try{}catch{}finally{dispose}. Effective c# has an item on this and I bet you willget 10+ similar answers.

http://www.amazon.com/Effective-Specific-Ways-Improve-Your/dp/0321245660

Answer 7

The using statement defines a scope in which to use an object which implements the IDisposable interface. The object will be cleaned up once the block has been exited. See:

http://msdn.microsoft.com/en-us/library/yh598w02.aspx

Answer 8

See http://msdn.microsoft.com/en-us/library/yh598w02(VS.80).aspx

The using statement encapsulates variables inside of it in a scope. When the execution exits the using block, all objects inside of it are disposed from memory. You might see it with DB connections so that when the using block exits the resources allocated to that connection are cleaned up and closed.