dcsimg
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

Tip: Using the Obsolete Class to Signal Upcoming Changes

See how to use the Obsolete Class to let your vendors know of upcoming changes that could break their code.


advertisement

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


Often, assemblies are distributed to vendors to consume your code. Changes to such assemblies are always hectic to manage. If we are removing or switching methods or properties in a class, you can mark them with the ObsoleteAttribute decorator. See below for an example:

//we are marking the below property "King" as obsolete

[ObsoleteAttribute("This property will be removed soon. Please switch to Emperor.", false)]

public static string King

{ get { return "king"; } }


//we are going to use this in future.

public static string Emperor

{ get { return "emperor."; } }Using Obsolete class to let your vendors know of the upcoming changes that could break their code


   
Srinath M. S. says: "I would love to leave a footprint in this flat world."
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date