.NET Tip: Managing Resources with the Using Statement San Antonio 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

SoloComputers.com
915-204-8163
7903 Pinebrook Dr.
San Antonio, TX
Tek Systems
(210) 384-3030
1100 NW Loop 410
San Antonio, TX
I S Systems
(210) 564-9300
5121 Crestway Dr Ste 412
San Antonio, TX
E-Lan Resources
(210) 599-4277
9330 Corporate Dr
San Antonio, TX
Q A Solutions Inc
(210) 348-7131
1603 Babcock Rd Ste 254
San Antonio, TX
Frontline Systems Inc
(210) 822-0494
8610 Broadway St Ste 280
San Antonio, TX
Petrich Consulting
(210) 657-3851
5123 Sirretta Dr
San Antonio, TX
Ccmcs Inc
(210) 495-8812
14607 San Pedro Ave
San Antonio, TX
Ocasio Computer Consulting
(210) 545-5539
San Antonio, TX
Tech Now Computer Training
(210) 732-1242
4243 E Piedras Dr Ste 250
San Antonio, 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

SoloComputers.com

915-204-8163
7903 Pinebrook Dr.
San Antonio, TX
http://SoloComputers.com

Related Local Event
2009 IEEE International Conference on Systems, Man and Cybernetics - SMC
Dates: 10/11/2009 - 10/14/2009
Location: Hyatt Regency Riverwalk
San Antonio, TX
View Details