.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Nashville TN

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

Crosslin & Associates PC
615-320-5500
2525 W End Ave
Nashville, TN
Advanced Network Solutions
615-277-0500
105 Broadway
Nashville, TN
Peachtree Software Support
615-256-1111
415 4th Ave S
Nashville, TN
Advanced Technical Services
615-747-5810
200 Hill Ave
Nashville, TN
Computer Services
615-252-8044
230 Willow St
Nashville, TN
Affiliated Computer Services
615-874-3000
801 Royal Pkwy
Nashville, TN
Computer Repair
615-882-9446
2744 Old Lebanon RD
Nashville, TN
Cumberland Technical Services
615-297-6815
420 Elmington Ave
Nashville, TN
Cyberangel Security Solutions Inc
615-837-9191
475 Metroplex DR
Nashville, TN
Cbnc LLC
615-831-3270
5360 Edmondson Pike
Nashville, TN

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

Crosslin & Associates PC

615-320-5500
2525 W End Ave
Nashville, TN

Related Local Events
Christians In Action Trade Show
Dates: 10/16/2009 - 10/17/2009
Location: Gaylord Opryland Resort & Convention Center
Nashville, TN
View Details

MS PowerPoint 2002 (XP) Level Two
Dates: 7/16/2009 - 7/16/2009
Location: Greater Nashville Association of Realtors
Nashville, TN
View Details

Intergraph 2009
Dates: 6/15/2009 - 6/18/2009
Location: Gaylord Opryland Resort & Convention Center
Nashville, TN
View Details