.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Charlotte NC

Here is encapsulation, one of the very basic tenets of object-oriented programming. Using properties instead of public variables helps insulate the users of your class from change, provides you more flexibility, and will ease maintenance of your class.

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
Charlotte Systems Company
(704) 770-0077
Charlotte, NC

provided by: 
Originally published at Internet.com


I have run across some old code recently where some classes exposed public variables directly to the outside world. Even though the code works, it is very fragile. The code looked something like this: public class Person { public string Name; public int Age; }

A much better practice is to make class variables private and expose them through public properties, thus encapsulating the details of your implementation. This brings several benefits, including that ability to override the property in derived classes or to easily add validation logic when the property value is set. You also can create calculated properties whose values are determined only when they are accessed. A version of the Person class using properties might look like this: public class Person { private string _Name; private int _Age; public string Name { get { return _Name; } set { _Name = value; } } public int Age { get { return _Age; } set { _Age = value; } } }

As you can see, using properties does take several more lines of code than exposing public variables. The cost, though, is well worth the benefit to your application. If you are using Visual Studio 2008, you can use the new support for the automatic properties to gain the benefit of properties with syntax that is very similar to using public variables. Here is the Person class in Visual Studio 2008 using automatic properties: public class Person { public string Name { get; set; } public int Age { get; set; } }

In the long run, I think you will find that using properties makes your classes more stable and easier to extend.

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