.NET Tip: Managing Resources with the Using Statement Albany NY

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

CompareTechProviders.com
518-207-3445
5 Washington Place
Troy, NY
Computer Visions
(518) 437-1600
16 Corporate Woods
Albany, NY
Softtek Integration Systems Inc
(518) 464-9344
1500 Central Ave
Albany, NY
T I M Formation Inc
(518) 456-6211
1913 Central Ave Ste 1
Albany, NY
Comsys Technical Svcs Inc
(518) 458-6145
125 Wolf Rd
Albany, NY
Cgi-Ams
(518) 218-7700
100 Great Oaks Blvd
Albany, NY
I Mg
(518) 482-0558
8 Automation Ln
Albany, NY
Lauren Group Llc the
(518) 453-1635
98 Wolf Tcby Rd
Albany, NY
Brainstorm-Micro
(518) 433-1250
11 Pruyn St
Albany, NY
Tos Systems Inc
(518) 869-5009
210 Washington Avenue Ex
Albany, NY

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

CompareTechProviders.com

Compare providers of business essential software solutions. Request information, pricing from multiple providers.

518-207-3445
5 Washington Place
Troy, NY
CompareTechProviders.com

Review and compare providers of business essential software solutions. Request information, pricing and demos from multiple providers. Make the right choice for your business.

Related Local Event
Thirty Low/No-Cost Things to Keep Your Computers and Network Running Smoothly
Dates: 7/21/2009 - 7/21/2009
Location: Albany-Colonie Regional Chamber of Commerce
Albany, NY
View Details