.NET Tip: Managing Resources with the Using Statement Austin TX

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

Lone Star Internet
512-708-8006
211 E 7th Ste 1110
Austin, TX
Adhesive Software
512-478-7349
800 Brazos St
Austin, TX
Austin Programming Solutions
512-990-2151
900 Congress Avenue
Austin, TX
Activant Solutions Inc
512-328-2300
804 Las Cimas Pkwy
Austin, TX
MicroMain Corporation
512-328-3235
5100 Bee Caves Road
Austin, TX
MicroMain Corporation
523-328-3235
5100 Bee Caves Road
Austin, TX
Terminal B Information Technology Services
512-381-4800
108 Wild Basin Road, Suite 255, Austin, TX 78746
Austin, TX
Mojica PC Solutions
512-300-9956
614 S 1st Street
Austin, TX
Parts-People.Com Inc
512-339-1990
3106 Industrial Terrace
Austin, TX
IQgistics
512.535.4165
5900 Southwest Parkway
Austin, TX

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

Lone Star Internet

512-708-8006
211 E 7th Ste 1110
Austin, TX
http://www.lone-star.net

Related Local Events
Renewable Energy World Conference & Expo North America
Dates: 2/23/2010 - 2/25/2010
Location: Austin Convention Center, Austin
Austin, TX
View Details

Lone Star Ruby Conference 2009
Dates: 8/27/2009 - 8/29/2009
Location: Norris Conference Center
Austin, TX
View Details