Question

I saw people can add Obsolete if a class/method is not recommended or will be deleted soon.

[Obsolete("Crap, dont use it, we have something better", true)]

Is there something for unfinished/untested classes? I mean I have here a class and this class will do soon a lot of good stuff and everybody should use it – its just not finished yet. Another class that is finished but not tested 100%. Can I add something like:

[Whatever("not tested yet... whatever", true)]

Or what else could I choose?

Answer 1

There are no such attributes as a [WillBeAvailableSoon] or [Untested] or [Whatever] in the .NET-framework. The best thing would be to publish the class when it is fully implemented and tested, as mentioned by Paolo.

You could however use the ObsoleteAttribute in a manner that would not generate a compiler-error but still a warning, using a custom text:

[Obsolete("This method is untested and will be stable after Release 1.2", false)]
public void DoSomething()
{
    throw new NotImplementedException();
}

Though I personally strongly suggest to go with Paolo’s advice…

Given that you are having your code in some source control system you won’t need to worry about anyone using your unstable code. Everything that is checked in should be compile clean, but there’s no need for it to be fully implemented or tested. Your fellow team-mates will hopefully know what you are working on and that you may potentially check in unstable code to enable your colleagues to continue your work if you get ill overnight or anything like that…