I realize that it seems to be a duplicate of What is the difference between a Field and a Property in C#? but my question has a slight difference (from my point of view):
Once I know that
- I will not use my class with "techniques that only works on properties" and
- I will not use validation code in the getter/setter.
Is there any difference (except the style/future development ones), like some type of control in setting the property?
Is there any additional difference between:
public string MyString { get; set; }
and
public string myString;
(I am aware that, that the first version requires C# 3.0 or above and that the compiler does create the private fields.)
ベストアンサー1
Fields and properties look the same, but they are not. Properties are methods and as such there are certain things that are not supported for properties, and some things that may happen with properties but never in the case of fields.
Here's a list of differences:
- Fields can be used as input to
out/refarguments. Properties can not. - A field will always yield the same result when called multiple times (if we leave out issues with multiple threads). A property such as
DateTime.Nowis not always equal to itself. - Properties may throw exceptions - fields will never do that.
- Properties may have side effects or take a really long time to execute. Fields have no side effects and will always be as fast as can be expected for the given type.
- Properties support different accessibility for getters/setters - fields do not (but fields can be made
readonly) - When using reflection the properties and fields are treated as different
MemberTypesso they are located differently (GetFieldsvsGetPropertiesfor example) - The JIT Compiler may treat property access very differently compared to field access. It may however compile down to identical native code but the scope for difference is there.