dcsimg
Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: .NET
Expertise: Intermediate
Aug 7, 2018

WEBINAR:

On-Demand

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


Using the Obsolete Class to Signal Upcoming Changes

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
 
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