.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Saint Louis MO

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

Open Software Technology
314-854-9138
7777 Bonhomme Ave
St. Louis, MO
Engineering Software International
314-352-4700
4545 Oleatha Ave
St. Louis, MO
New Horizons Software Inc
314-961-4335
801 Leonard DR
St. Louis, MO
E Data Solutions Inc
314-446-1555
315 Lemay Ferry RD
St. Louis, MO
Bemas Software Inc
314-439-5300
7 The Pines CT
St. Louis, MO
Digital Consulting & Software
314-682-2350
12655 Olive Blvd
St. Louis, MO
Foundry Software Development Co
314-993-3732
721 Emerson RD
St. Louis, MO
Wonderware Central
888-676-9933
Two City Place Drive
St. Louis, MO
STL EHR Group
314-477-7459
689 Craig Road
Creve Coeur, MO
Client Server Solutions Inc
314-523-4400
2008 Altom CT
St. Louis, MO

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

Open Software Technology

314-854-9138
7777 Bonhomme Ave
St. Louis, MO