.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Raleigh 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

Net@Work
919-781-2900
1616 East Millbrook Road
Raleigh, NC
Devco Software Solutions
919-573-6060
3737 Glenwood Ave
Raleigh, NC
Diebold Software Solutions Inc
919-788-8665
8024 Glenwood Ave
Raleigh, NC
Argent Software Inc
919-573-6161
3737 Glenwood Ave
Raleigh, NC
Advanced Information Solutions
919-848-4440
9207 Baileywick RD
Raleigh, NC
Altitude Software
919-845-7010
8601 Six Forks RD
Raleigh, NC
C C Intelligent Solutions
919-844-2111
7701 Six Forks RD
Raleigh, NC
Alien Skin Software
919-832-4065
1121 Haynes St
Raleigh, NC
Blue Lizard Technologies, inc.
(919) 858-8885
1151 Executive Circle
Cary, NC
Racarie Software
919-654-4560
201 Shannon Oaks Circle
Cary, 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

Net@Work

919-781-2900
1616 East Millbrook Road
Raleigh, NC

Related Local Events
North Carolina Legislative Holiday Reception (Govt. Affairs)
Dates: 12/3/2009 - 12/3/2009
Location: Washington Duke Inn & Golf Club
Durham, NC
View Details

North Carolina Legislative Holiday Reception (Govt. Affairs)
Dates: 12/3/2009 - 12/3/2009
Location: Washington Duke Inn & Golf Club
Durham, NC
View Details

Breakfast & Business (PWN)
Dates: 11/24/2009 - 11/24/2009
Location: Durham Chamber
Durham, NC
View Details

Breakfast & Business (PWN)
Dates: 11/24/2009 - 11/24/2009
Location: Durham Chamber
Durham, NC
View Details

Lunch & Learn (SBC)
Dates: 11/11/2009 - 11/11/2009
Location: Durham Chamber
Durham, NC
View Details