Attributes on interface property not enforced on concrete class

[Steve K.]

I added a property to an interface like this:
<code>
public interface ISimpleAddress
{
[Bindable(BindableSupport.Yes)]
[EditorBrowsable(EditorBrowsableState.Always)]
string CarrierFax{ get; set; }
}
</code>

I was disappointed to see that when I implemented the interface:
1) Visual Studio Refactoring-Auto-Implement tool didn't add the attributes
2) If I omitted the attributes from the concrete class the compiler didn't
complain.

Why do interfaces allow attributes if they won't be enforced?

Anyone know?

[Jesse McGrew]

On Jan 19, 11:07 pm, "Steve K." <[e-mail]:

I added a property to an interface like this:
<code>
public interface ISimpleAddress
{
[Bindable(BindableSupport.Yes)]
[EditorBrowsable(EditorBrowsableState.Always)]
string CarrierFax{ get; set; }}

</code>

I was disappointed to see that when I implemented the interface:
1) Visual Studio Refactoring-Auto-Implement tool didn't add the attributes
2) If I omitted the attributes from the concrete class the compiler didn't
complain.

Why do interfaces allow attributes if they won't be enforced?

Anyone know?

Attributes on an interface member aren't part of the interface
contract, they're modifiers for the member as *part of that
interface*. For example, you might use an attribute to affect whether
CarrierFax is displayed in the IntelliSense list for an ISimpleAddress
variable.

Jesse