.NET Tip: Managing Resources with the Using Statement Honolulu HI

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

Laser Barcode Solutions
(808) 591-0031
1314 S King St Suite 424
Honolulu, HI
Success Solutions LLC
(808) 946-0005
1311 Kapiolani Blvd
Honolulu, HI
Century Computers Inc
(808) 585-0444
500 Ala Moana Blvd
Honolulu, HI
City and County Offices Human Resources Department
(808) 523-4121
650 S King St
Honolulu, HI
Compusultants Inc
(808) 545-1216
1188 Bishop St
Honolulu, HI
Computer 1 Associates Inc
(808) 524-6700
1188 Bishop St
Honolulu, HI
Computer Associates International Inc
(808) 585-0057
1132 Bishop St
Honolulu, HI
Human Touch Software Co
(808) 924-3930
2222 Kalakaua Ave
Honolulu, HI
Analyzer USA Inc
(808) 922-4620
2155 Kalakaua Ave
Honolulu, HI
Retail Solutions Inc
(808) 834-1100
2828 Paa St
Honolulu, HI

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

Laser Barcode Solutions

(808) 591-0031
1314 S King St Suite 424
Honolulu, HI

Related Local Events
GLOBECOM 2009 - 2009 IEEE Global Telecommunications Conference
Dates: 11/30/2009 - 12/4/2009
Location: Hilton Hawaiian Village
Honolulu, HI
View Details

2009 IEEE International Professional Communication Conference (IPCC 2009)
Dates: 7/19/2009 - 7/22/2009
Location: Hilton Hawaiian Village
Honolulu, HI
View Details

Plant Biology 2009
Dates: 7/18/2009 - 7/22/2009
Location: Hawaii Convention Center
Honolulu, HI
View Details

Plant Biology 2009
Dates: 7/18/2009 - 7/22/2009
Location: Honolulu Convention Center
Honolulu, HI
View Details