Home/ Questions/Q 273911
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T00:31:45+00:00

I am converting an open source Java library to C#, which has a number

  • 0

I am converting an open source Java library to C#, which has a number of methods and classes tagged as deprecated. This project is an opportunity to start with a clean slate, so I plan to remove them entirely. However, being new to working on larger projects, I am nervous that the situation will arise again. Since much of agile development revolves around making something work now and refactoring later if needed, it seems like deprecation of APIs must be a common problem. Are there preventative measures I can take to avoid/minimize API deprecation, even if I am not entirely sure of the future direction of a project?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m not sure there is much you can do. Requirements change, and if you absolutely have to make sure that clients of the API are not broken by newer API version, you’ll have rely on simply deprecating code until you think that no-one is using the deprecated code.

    Placing [Obsolete] attributes on code causes the compiler to create warnings if there are any references to the obsolete methods. This way clients of the API, if they are diligent about fixing their compiler warnings, can gradually move to the new methods without having everything break with the new version.

    Its useful if you use the ObsoleteAttribute’s override which takes a string:

    [Obsolete("Foo is deprecated. Use Bar instead for munging widgets.")]

    <frivolous>

    Perhaps you could create a TimeBombAttribute:

    [TimeBomb(new DateTime(2010,1,1), "Foo will blow up! Better use Bar, or else."]

    In your code, reflect for methods with the timebomb attribute and throw KaboomException if they are called after the specified date. That’ll make sure that after 1st January 2010 no-one is using the obsolete methods, and you can clean up your API nicely. 🙂

    </frivolous>

    • 0