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

Inspironix, Inc
(916) 488-3222
3400 Cottage Way, Suite L
Sacramento, CA
Brainware Solutions Inc
(916) 273-6652
2929 Fulton Avenue, Suite 2967-2
Sacramento, CA
Brainware Solutions Inc
(916) 273-6652
2929 Fulton Avenue, Suite 2976-2
Sacramento, CA
Maintenance Connection
888-567-3434
1477 Drew Ave, #103
Davis, CA
Agreeya Solutions
916-351-2576
110 Woodmere Road
Folsom, CA
Delta Business Solutions
(916) 930-1939
1717 4th Ave
Sacramento, CA
Paradigm Systems Inc
(916) 446-4958
1107 9th St Ste T100
Sacramento, CA
Hg Consulting Group Inc
(916) 492-1343
1415 L St Ste 890
Sacramento, CA
Full Speed Ahead Integrators Inc
(916) 924-3229
Sacramento, CA
Information Integration and Innovation Associates
(916) 492-9960
1005 12th D St
Sacramento, 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

Inspironix, Inc

9164883222
3400 Cottage Way, Suite L
Sacramento, CA