.NET Tip: Data Encapsulation: Using Properties Instead of Public Variables Honolulu HI

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

Laser Barcode Solutions
(808) 591-0031
1314 S King St Suite 424
Honolulu, HI
Success Solutions LLC
(808) 946-0005
1311 Kapiolani Blvd
Honolulu, HI
Century Computers Inc
(808) 585-0444
500 Ala Moana Blvd
Honolulu, HI
City and County Offices Human Resources Department
(808) 523-4121
650 S King St
Honolulu, HI
Compusultants Inc
(808) 545-1216
1188 Bishop St
Honolulu, HI
Computer 1 Associates Inc
(808) 524-6700
1188 Bishop St
Honolulu, HI
Computer Associates International Inc
(808) 585-0057
1132 Bishop St
Honolulu, HI
Human Touch Software Co
(808) 924-3930
2222 Kalakaua Ave
Honolulu, HI
Analyzer USA Inc
(808) 922-4620
2155 Kalakaua Ave
Honolulu, HI
Retail Solutions Inc
(808) 834-1100
2828 Paa St
Honolulu, HI

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

Laser Barcode Solutions

(808) 591-0031
1314 S King St Suite 424
Honolulu, HI

Related Local Events
GLOBECOM 2009 - 2009 IEEE Global Telecommunications Conference
Dates: 11/30/2009 - 12/4/2009
Location: Hilton Hawaiian Village
Honolulu, HI
View Details

2009 IEEE International Professional Communication Conference (IPCC 2009)
Dates: 7/19/2009 - 7/22/2009
Location: Hilton Hawaiian Village
Honolulu, HI
View Details

Plant Biology 2009
Dates: 7/18/2009 - 7/22/2009
Location: Hawaii Convention Center
Honolulu, HI
View Details

Plant Biology 2009
Dates: 7/18/2009 - 7/22/2009
Location: Honolulu Convention Center
Honolulu, HI
View Details