.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Cincinnati OH

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

3D Computer Systems
513-569-0500
2230 Auburn Ave
Cincinnati, OH
The Shepherd Chemical Co.
(513) 731-1110
4900 Beech Street
Norwood, OH
A-Hi Computers & Electronics
(513) 531-1111
4030 Montgomery Road
Cincinnati, OH
Netburg Consulting Services
513-247-9701
150 E 4th Street
Cincinnati, OH
Graphic Informatn Systems Inc
513-948-1300
7633 Production Dr
Cincinnati, OH
21st Century Designs Inc.
(513) 662-5862
P.O. Box 112091
Cincinnati, OH
Greater Cincinnati Computer
513-985-1300
7024 Plainfield Rd
Cincinnati, OH
Cincinnati PC Solutions
513-871-3600
4770 Redbank Expressway
Cincinnati, OH
Chemical Systems International Inc.
(513) 385-6688
3567 Blue Rock Road
Cincinnati, OH
MIKAL Salon and Spa Computers
513-528-5100
4382 Mt Carmel Tobasco Rd
Cincinnati, OH

 

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

3D Computer Systems

513-569-0500
2230 Auburn Ave
Cincinnati, OH

Related Local Event
Forge Fair 2010
Dates: 4/20/2010 - 4/22/2010
Location: Cincinnati Convention Center
Cincinnati, OH
View Details