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

SoloComputers.com
915-204-8163
7903 Pinebrook Dr.
San Antonio, TX
I S Systems
(210) 564-9300
5121 Crestway Dr Ste 412
San Antonio, TX
E-Lan Resources
(210) 599-4277
9330 Corporate Dr
San Antonio, TX
Q A Solutions Inc
(210) 348-7131
1603 Babcock Rd Ste 254
San Antonio, TX
Frontline Systems Inc
(210) 822-0494
8610 Broadway St Ste 280
San Antonio, TX
Petrich Consulting
(210) 657-3851
5123 Sirretta Dr
San Antonio, TX
Ccmcs Inc
(210) 495-8812
14607 San Pedro Ave
San Antonio, TX
Ocasio Computer Consulting
(210) 545-5539
San Antonio, TX
Tech Now Computer Training
(210) 732-1242
4243 E Piedras Dr Ste 250
San Antonio, TX
Ynl Consulting
(210) 340-0098
7550 W Ih 10
San Antonio, 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

SoloComputers.com

915-204-8163
7903 Pinebrook Dr.
San Antonio, TX
http://SoloComputers.com

Related Local Event
2009 IEEE International Conference on Systems, Man and Cybernetics - SMC
Dates: 10/11/2009 - 10/14/2009
Location: Hyatt Regency Riverwalk
San Antonio, TX
View Details