.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Dallas TX

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

Videotex Systems
972 231 9200 x124
10255 Miller Road
Dallas, TX
elKore Inc
1-877-355-6731
12225 Greenville Avenue
Dallas, TX
Information Processing Corporation
972-404-9244
13747 Montfort, Suite 300
Dallas, TX
Maxtrus Micro
(800) 910-2380
4781 Snow Dr
Mesquite, TX
Spatial Data Inc.
972-791-0911
4545 Fuller Drive
Irving, TX
C. Pitman Baker & Associates
972-579-1642 X 227
1431 Greenway Dr.
Irving, TX
In2 Solutions Inc
(972) 494-7400
3534 W Walnut St
Garland, TX
P O Express Inc
(972) 272-0603
3717 Burning Tree Ln
Garland, TX
Sixred, Inc.
(972) 365-3437
15950 North Dallas Parkway
Dallas, TX
Freeman Software
(972) 840-1119
506 Valencia Dr
Garland, TX

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

Videotex Systems

972 231 9200 x124
10255 Miller Road
Dallas, TX
http://www.videotexsystems.com/

Related Local Events
Unconventional Gas Conference & Exhibition
Dates: 9/29/2009 - 10/1/2009
Location: Fort Worth Convention Center
Fort Worth, TX
View Details

Tech Titans Fast Tech Awards Gala
Dates: 8/28/2009 - 8/28/2009
Location: Renaissance Dallas Richardson Hotel
Richardson, TX
View Details