.NET Tip: Managing Resources with the Using Statement Cincinnati OH

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

3D Computer Systems
513-569-0500
2230 Auburn Ave
Cincinnati, OH
The Shepherd Chemical Co.
(513) 731-1110
4900 Beech Street
Norwood, OH
A-Hi Computers & Electronics
(513) 531-1111
4030 Montgomery Road
Cincinnati, OH
Netburg Consulting Services
513-247-9701
150 E 4th Street
Cincinnati, OH
Graphic Informatn Systems Inc
513-948-1300
7633 Production Dr
Cincinnati, OH
21st Century Designs Inc.
(513) 662-5862
P.O. Box 112091
Cincinnati, OH
Greater Cincinnati Computer
513-985-1300
7024 Plainfield Rd
Cincinnati, OH
Cincinnati PC Solutions
513-871-3600
4770 Redbank Expressway
Cincinnati, OH
Chemical Systems International Inc.
(513) 385-6688
3567 Blue Rock Road
Cincinnati, OH
MIKAL Salon and Spa Computers
513-528-5100
4382 Mt Carmel Tobasco Rd
Cincinnati, OH

 

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

3D Computer Systems

513-569-0500
2230 Auburn Ave
Cincinnati, OH

Related Local Event
Forge Fair 2010
Dates: 4/20/2010 - 4/22/2010
Location: Cincinnati Convention Center
Cincinnati, OH
View Details