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

Collabera
(704) 372-7272
212 South Tryon Street
Charlotte, NC
CompuData, Inc
(704) 504-0600
2401 Whitehall Park Drive
Charlotte, NC
SunGard Asset Management Systems
(704) 527-6300
PO Box 240882
Charlotte, NC
Oracle Corporation
(704) 423-1450
2550 West Tyvola Road
Charlotte, NC
StreamLogic Inc.
704-771-1090
3030 Glen Summit Dr.
Charlotte, NC
Ironworks Consulting, LLC
(704) 494-8889
3440 Toringdon Way, Suite 205
Charlotte, NC
InterDyn Artis
(704) 846-6750
8100 Tower Point Drive
Charlotte, NC
A3 Technologies, Inc
704-708-3872
2300 sardis Rd North
Charlotte, NC
Software Toolbox Inc
(704) 849-2773
148A East Charles Street
Charlotte, NC
Gallagher Systems Group Inc
(704) 752-3881
Charlotte, 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

Collabera

(704) 372-7272
212 South Tryon Street
Charlotte, NC

Related Local Events
Automation Technology Expo South
Dates: 4/28/2010 - 4/29/2010
Location: Charlotte Convention Center
Charlotte, NC
View Details

Green Manufacturing Expo-Charlotte
Dates: 4/28/2010 - 4/29/2010
Location: Charlotte Convention Center
Charlotte, NC
View Details

Technology Summit: Technology + Innovation = Our Future
Dates: 11/18/2009 - 11/18/2009
Location: Hilton Charlotte Center City
Charlotte, NC
View Details

NCTA Congressional Briefing: Featuring U.S. Representatives Sue Myrick and Larry Kissell
Dates: 11/2/2009 - 11/2/2009
Location: Charlotte Chamber - Belk Action Center
Charlotte, NC
View Details

SOUTH-TEC
Dates: 10/6/2009 - 10/8/2009
Location: Charlotte Convention Center
Charlotte, NC
View Details