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

Apple Sales.com dba Mactown
(937) 435-0134
8975 Kingsridge Drive
Dayton, OH
Modern Logics
(937) 885-4923
801 Saint Simons Ln
Dayton, OH
Ncr Corporation
(937) 445-1488
1611 S Main St
Dayton, OH
Paramount Global Solutions Inc
(937) 428-6669
1458 Yankee Park Pl
Dayton, OH
Ncr Corporation
(937) 445-5000
1700 S Patterson Blvd
Dayton, OH
Firstmark-Pi Tech
(937) 299-7722
Dayton, OH
Stg Inc
(937) 259-0074
5100 Springfield St
Dayton, OH
Rhi Consulting
(937) 224-7442
5 Three Ctr
Dayton, OH
Abacus Technology Corp
(937) 427-1002
4141 Colonel Glenn Hwy
Dayton, OH
Softronics
(937) 427-2272
4027 Colonel Glenn Hwy Ste 200
Dayton, 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

Apple Sales.com dba Mactown

(937) 435-0134
8975 Kingsridge Drive
Dayton, OH

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