Properties vs. Fields: Need help grasping the uses of Properties over Fields

by

1) why I would want to use properties
instead of fields (especially when it
appears I am just adding additional
code

You should always use properties where possible. They abstract direct access to the field (which is created for you if you don’t create one). Even if the property does nothing other than setting a value, it can protect you later on. Changing a field to a property later is a breaking change, so if you have a public field and want to change it to a public property, you have to recompile all code which originally accessed that field.

2) any tips on recognizing the use of
properties and not seeing them as
simply methods (with the exception of
the get;set being apparent) when
tracing other peoples code?

I’m not totally certain what you are asking, but when tracing over someone else’s code, you should always assume that the property is doing something other than just getting and setting a value. Although it’s accepted practice to not put large amounts of code in getters and setter, you can’t just assume that since it’s a property it will behave quickly.

3) Any general rules of thumb when it
comes to good programming methods in
relation to when to use what?

I always use properties to get and set methods where possible. That way I can add code later if I need to check that the value is within certain bounds, not null etc. Without using properties, I have to go back and put those checks in every place I directly accessed the field.

More Related Contents:

  1. Any reason to use auto-implemented properties over manual implemented properties?
  2. What is the difference between a field and a property?
  3. Public Fields versus Automatic Properties
  4. Difference between Property and Field in C# 3.0+
  5. Auto-implemented getters and setters vs. public fields
  6. Why won’t anyone accept public fields in C#?
  7. c# – How to iterate through classes fields and set properties
  8. Overriding fields or properties in subclasses
  9. What is the best practice for using public fields?
  10. C# software freezing when setting property to true
  11. Properties vs Methods
  12. Comparing object properties in c# [closed]
  13. Can I change a private readonly field in C# using reflection?
  14. Raise an event whenever a property’s value changed?
  15. Get properties in order of declaration using reflection
  16. Why use ‘virtual’ for class properties in Entity Framework model definitions?
  17. Thread-safe List property
  18. How to implement a read only property
  19. How to hide an inherited property in a class without modifying the inherited class (base class)?
  20. “Strange” C# property syntax
  21. How to hide public methods from IntelliSense
  22. Best practices: throwing exceptions from properties
  23. c# marking class property as dirty
  24. How to check all properties of an object whether null or empty?
  25. Are accessors (get and set functions) popular with C++ programmers?
  26. C#: Difference between List and Collection (CA1002, Do not expose generic lists) [duplicate]
  27. Getters and Setters are bad OO design? [duplicate]
  28. C# 3.0 Auto-Properties – Is it possible to add custom behaviour?
  29. Custom browsable property for Form at design time
  30. Pass property itself to function as parameter in C#

Leave a Comment