Library tutorials & articles

Attributed Programming in .NET Using C#

Intrinsic and Custom Attributes

.NET framework is littered with attributes and CLR (common language runtime) provides a set of intrinsic attributes that are integrated into the framework. Serializable is an example of intrinsic attribute. Besides the framework supplied attributes, you can also define your own custom attributes to accomplish your goal.

When do you define your custom attributes? Attributes are suitable when you have crosscutting concerns. Object Oriented (OO) methodology lacks a modular approach to address crosscutting concerns in objects. Serialization is an example of crosscutting concern. Any object can be either serializable or non-serializable. If, for example, halfway in the development phase you realize that you need to make a few classes serializable, how do you do that? In .NET, you only need to mark them as serializable and provide methods to implement a serialization format. Other crosscutting concerns can be security, program monitoring and recording during debugging, data validation, etc. If you have a concern that affects a number of unrelated classes, you have a crosscutting concern and attributes are excellent candidates to address crosscutting concerns.

Comments

  1. 03 May 2004 at 03:26

    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

  2. 06 Mar 2004 at 17:38
    how can I Add a reference to assembly System.Runtime.Serialization.Formatters.Soap.dll ???
  3. 10 Jan 2003 at 05:52
    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.
  4. 06 Jan 2003 at 15:36

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

  5. 12 Nov 2002 at 17:52
    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.
  6. 31 Oct 2002 at 07:28

    The article is nice

  7. 01 Jan 1999 at 00:00

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

Leave a comment

Sign in or Join us (it's free).

Deepak Dutta

Related podcasts

  • A Practical Look at Silverlight 2 Part 1

    Now that Silverlight 2 is at the Olympics and making a big splash, we wanted to explore this fascinating technology more. Microsoft Silverlight 2 is a cross-browser, cross-platform, and cross-device plug-in for delivering the next generation of .NET based media experiences and rich interactive ap...

Events coming up

  • Dec 9

    GL.net Group Meeting - December 2009

    Gloucester, United Kingdom

    The beginning of this year holiday season will belong to mocks. Ronnie and Stephen will take us for a tour around exciting world of unit testing.

We'd love to hear what you think! Submit ideas or give us feedback