Is there a performance difference between setting a field by a method AND setting it by property?

Question

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)

@Oded: I did :) Now I can see that property seems to be slower — pencilCake, Mar 08 '12 at 11:09
If there is a performance difference it must be measurable in µs so you should use the more understandable way rather than the most efficient. — remi bourgarel, Mar 08 '12 at 11:11

score 2 · Accepted Answer · answered Mar 08 '12 at 11:04

Properties are methods. If you declare a property named MyProperty with both get/set then the compiler will emit two methods: get_MyProperty and set_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".

Is there a performance difference between setting a field by a method AND setting it by property?

1 Answers1