This thread is for discussions of Attributed Programming in .NET Using C#.

The article is nice

Well the attributed programming started from MIDL/COM programming and .NET also supports this concept widely.
The advantages provided with attributed programming is amazing and simultaneously it has a drawback.
The growth of attributes in each model like MIDL,MTS/COM+ and .NET is quite alarming.It increases the learning curve for a developer to use that Runtime.
And it seems whatever the runtime Environment is not able to do is kept as attributes and Developer has to provide it.

For example
void  GetData(CMyObject  obj1,CMyObject  &obj2);

In the above method all C++ compiler recognizes that obj1 is passed by value and obj2 is passed by reference.If the Runtime environment can have the equivalent inteligence then no requirement of marking [SERIALIAZABLE] attribute to the class if we want to pass the object by value.
And what ever feature is not provided by any of the existing Object Oriented Language can be used as attributes.

Ghanshyam.

I have absolutely no knowledge of C# and attributes, but I could understand the article very easily.  Good Write-up!

This is a very good article.  

The example shown used public modifier for the class attributes, is there any way to get it to work with private/protected attributes?  I tried the example code using private and was unable to get it to work.

how can I Add a reference to assembly System.Runtime.Serialization.Formatters.Soap.dll ???

Hi
Good article.I have a qus here. I have used a ot of attributes and have tried writing mine as well. Now the basic qus of when to write one of our own is still a little difficult for me. I understand simple using [SERIALIZABLE] makes life easier, but to really appreciate this perhaps I would want to understand whats the tought way of doing the same.
Could anybody explain with an example how attribute is giving ab advantage.

Thanks
sourabh