.NET Tip: Managing Resources with the Using Statement Pittsburgh PA

Take control of the lifetime of your objects. Release your object's resources on your schedule, not when the CLR determines they are no longer needed.

Local Companies

Shared Software Solutions
412- 281-0790
812 Liberty Ave
Pittsburgh, PA
Cima Software
412- 573-0124
4606 Allegheny Center Mall
Pittsburgh, PA
Innovate Software
412- 681-3000
160 N Craig St
Pittsburgh, PA
Psychology Software Tools Inc
412- 271-5040
2050 Ardmore Blvd
Pittsburgh, PA
The Digital Accountant
412-580-2112
45 Tanager Drive
McKees Rocks, PA
Duerr Business Solutions Inc
412- 854-5876
71 Mcmurray Rd
Pittsburgh, PA
Automation Consulting Solutions
412- 318-8102
125 Hillvue Ln
Pittsburgh, PA
Global Business Solutions
412- 630-9111
109 Pineridge RD
Pittsburgh, PA
Iceburgh Solutions, LLC
412- 877-7114
4885A Mcknight Rd
Pittsburgh, PA
Selective Software Inc
412- 369-0480
100 Mcknight Park Dr
Pittsburgh, PA

provided by: 
Originally published at Internet.com


Last week, I showed you how you can help ensure that your objects release their resources by implementing IDisposable. This week, I want to show you the using statement that allows you to specify when your objects release their resources. Objects declared in the using statement will explicitly be disposed when the end of the using block is reached. I often use nested using statements for data access to precisely control the creation and disposal of my objects. Here is how you can take advantage of the using statement to create a database connection, create a command, and execute a data reader to access your data. using (SqlConnection CN = new SqlConnection("*** Your connection string here ***")) { CN.Open(); using (SqlCommand cmd = new SqlCommand("SELECT * FROM authors", CN)) { using (SqlDataReader dr = cmd.ExecuteReader()) { // Access elements items here } } }

By nesting the using statements above, you can be sure you are creating objects only when necessary and that, once everything is finished, your objects will all be disposed of in a timely manner. If an error should occur anywhere along the way, any objects created up to that point will still be disposed of when the using block is exited. The only caveat is that the object declared in the using statement must implement the IDisposable interface. Keep this in mind if you plan on taking advantage of the using statement with your own classes.

About the Author

Jay Miller is a Software Engineer with Electronic Tracking Systems, a company dedicated to robbery prevention, apprehension, and recovery based in Carrollton, Texas. Jay has been working with .NET since the release of the first beta and is co-author of Learn Microsoft Visual Basic.NET In a Weekend. Jay can be reached via email at jmiller@sm-ets.com.

Author: Jay Miller

Read article at Internet.com site

Featured Local Company

Shared Software Solutions

412- 281-0790
812 Liberty Ave
Pittsburgh, PA