.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Oakland CA

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

Propertyware
(415) 455-2400
575 Market St., Ste. 375
San Francisco, CA
International Business Machines Corporation
(415) 545-2000
425 Market St.
San Francisco, CA
ClearKite
(866) 894-8090
355 Berry St., Ste. 240
San Francisco, CA
Speller & Company LLC
415-848-3022
795 Folsom Street
San Francisco, CA
Mindjet Corporation
(415) 229-4200
1160 Battery St., 4th Flr
San Francisco, CA
OpCon Technologies, Inc.
(415) 439-5389
50 California St., Ste. 1500
San Francisco, CA
Science Applications International Corporation (SAIC)
(415) 202-1800
1275 Columbus Ave.
San Francisco, CA
Microsoft Corporation
(415) 972-6400
835 Market St., Ste. 700
San Francisco, CA
San Francisco Technologies, Inc.
(866) 992-2543
123 10th St.
San Francisco, CA
Streetline Networks
(650) 714-5528
995 Market St., 16th Flr.
San Francisco, CA

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

Propertyware

(415) 455-2400
575 Market St., Ste. 375
San Francisco, CA

Related Local Events
MACWORLD 2010
Dates: 1/4/2010 - 1/8/2010
Location: Moscone Convention Center
San Francisco, CA
View Details

Informex USA
Dates: 2/16/2010 - 2/19/2010
Location: Moscone Convention Center, San Francisco
San Francisco, CA
View Details

Advanced Lithography
Dates: 2/21/2010 - 2/26/2010
Location: San Jose Convention Center
San Jose, CA
View Details

Contraceptive Technology Conference : San Francisco
Dates: 3/24/2010 - 3/27/2010
Location: Hyatt Regency Hotel
San Francisco, CA
View Details

Web 2.0 Summit
Dates: 10/20/2009 - 10/22/2009
Location: Westin San Francisco Market Street
San Francisco, CA
View Details