.NET Tip: Managing Resources with the Using Statement Greensboro NC

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

L A Solutions
336-389-1707
110 E Washington St
Greensboro, NC
Software Design Inc
336-378-0900
1301 Carolina St
Greensboro, NC
Data Management Corp
336-275-1697
423 Eugene CT
Greensboro, NC
Compucon USA LLC
336-294-0604
620 Green Valley Rd
Greensboro, NC
COMPUTER TROUBLESHOOTING
336-510-7919
1400 Battleground Ave
Greensboro, NC
Spi Software Solutions
336-333-2967
2007 Yanceyville St
Greensboro, NC
Advantec Information Systems LLC
336-275-2832
2007 Yanceyville St
Greensboro, NC
D P Solutions Inc
336-854-7700
4411 W Market St
Greensboro, NC
Dalcom Consulting
336-851-1802
8 Oak Branch DR
Greensboro, NC
Engineered Software
336-299-4843
615 Guilford College RD
Greensboro, NC

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

L A Solutions

336-389-1707
110 E Washington St
Greensboro, NC
http://www.lasolutions.net