.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Birmingham AL

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

Visual Solutions Inc
205-930-5540
2217 10th CT S
Birmingham, AL
Westglenn Software
205-870-3118
2100 Southbridge Pkwy
Birmingham, AL
Martin Software Associates Inc
205-871-7766
4 Office Park Cir
Birmingham, AL
Cahaba Data Inc
205-262-9696
732 Montgomery Hwy 252
Birmingham, AL
Xcitek Solutions Plus LLC
205-439-5700
3595 Grandview Pkwy
Birmingham, AL
Arbitron Inc
205-977-6100
3500 Colonnade Pkwy
Birmingham, AL
Appsolute Genius
(205) 266-7981
3800 Colonnade Parkway
Birmingham, AL
Priority Software
205-838-7061
9006 4th Ave S
Birmingham, AL
Achaia Solutions
205-437-9960
117 Narrows Creek DR
Birmingham, AL
Exact Software North America
205-980-5270
3000 Eagle Point Corporate DR
Birmingham, AL

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

Visual Solutions Inc

205-930-5540
2217 10th CT S
Birmingham, AL

Related Local Event
Going Green Awards
Dates: 10/1/2009 - 10/1/2009
Location: Sheraton
North Birmingham, AL
View Details