Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Actual Performance of Fields vs. Properties
Is there a known performance difference between setting a field by method AND setting it via property?
(I just wonder if implementing a property emits some extra stuff to IL which makes the PROPERTY work slower than directly callind a method that sets the value)
Properties are methods. If you declare a property named
MyPropertywith both get/set then the compiler will emit two methods:get_MyPropertyandset_MyProperty, decorating them to make understandable to others (who will use the property) that that methods are getter/setter of a property. For example the first version of managed C++ didn’t hide this trick. Take a look to decompiled version of a method and a property setter (for example) and you’ll see they aren’t different, what you see in your code is sugar to make them “nice”.