CS0617: read-write attribute properties

[Jens Thiel]

Hi,

is there a reason for C# to require attribute arguments (properties) to be
read-write while VB and C++ are happy with only a setter?

Simplified Example:

public sealed class FooAttribute : Attribute
{
private string s;
public string Data { set { s = value; } };
}
[Foo(Data="bar")] won't work in C#, but in VB.NET and C++.

Jens.

--
http://ManagedXLL.net/ | http://jens-thiel.de/ | http://QuantLib.net/
Replace MSDN with my first name when replying to my email address!

[Jens Thiel]

""Jeffrey Tan[MSFT]"" <v-*****@online.mi crosoft.com> wrote

I have got a reply from Eric Gunnerson, the PROGRAM MANAGER of Visual C#.

As he said, It's a deliberate choice.
http://blogs.msdn.com/csharpfaq/arch...11/130236.aspx

But, I think this does not resolve the write-only problem. I have consulted him for write-only property issue. Thanks

Thanks Jeffrey, as I mentioned in my previous post I had already contacted
Eric on this. I received his blog link, but it's a misinterpration of the
issue. Eric is already aware of it.

Jens.
--
http://ManagedXLL.net/
Replace MSDN with my first name when replying to my email address!

[Jeffrey Tan[MSFT]]

Hi Jens,

Yes, that blog article only talks about the read-only issue, which did not
resolve write-only issue. So I contacted Eric for the write-only property
issue.

Today, I got the feedback from him, that is:
"In general, I'd expect that most attribute classes are just containers for
information and don't have any real logic in them, and that's why the
design is the way it is."

So the answer for this issue is that: This is an expected behavior, the
Visual C# development team choose this type of design.

Also, I have asked Eric about why VB.net allow write-only property. The
answer is these 2 languages are developed by different teams, and VB.net
team just choose another different design for it.

I hope all these makes sense to you. But if you still have any concern,
please feel free to feedback here, I will assist you.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Jeffrey Tan[MSFT]]

Hi Jens,

Does my reply make sense to you? Do you still have concern on this issue?

Please feel free to feedback. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.