In this post I have explained how you can use Obsolete attributes to mark some methods which are not no longer in used or may be remove in future release of the class. During the development cycle we may need to change the name or declaration of certain methods which may be using by some other developers. In this case if you changed the name or declaration of that method, application may crash in different point of times as it’s being used by other developer in the application. In this case you can use System.ObsoleteAttributes class to generate compiler warning and indicate the method as Obsolete.
Let’s discuss this with an example, Suppose we are having a Student Class which have GetStudentInfo() method which returns the students information.
Now this class is being used by many other developer to get the student information.
If you want to change the name or declaration of
To overcome this problem, and maintain the compatibility you can use “Obsolete” attributes to the old methods and define a new method and show a proper message to other developers.
This changes won’t be causes for any code break or application error. Other developers who are already using the GetStudentInfo() method will get an Compiler warning “Use GetStudentDetails Instead of GetStudentInfo” .
And for any new developer who are going to consume the GetStudentInfo() method will get an tool tip message that “Use GetStudentDetails Instead of GetStudentInfo”
Pingback: Dew Drop – January 31, 2011 | Alvin Ashcraft's Morning Dew
You made some good points there. I did a search on the topic and found most people will agree with your blog.
Hi there, I found your blog via Google while searching for first aid for a heart attack and your post looks very interesting for me.