Create [WarningAttribute] and [ErrorAttribute] that triggers compiler warnings/errors the way [ObsoleteAttribute] does.

FEATUREREQUEST COMPILER

Add a [WarningAttribute] or [CompilerWarningAttribute] and [CompilerErrorAttribute] that works the same way as [ObsoleteAttribute]; it would trigger a compiler warning or error with a customized message. Ideally it would not be sealed. You could do things like:

[Warning("This class uses PInvoke and will prevent ARM compatibility.")]

[Experimental("This method has not completed Quality Assurance, and should not be used in a production environment.")] 

This feature would be particularly useful for component creators.

This would be the bees’ knees.

[WarningAttribute] on UserVoice

[jmarolf]

I am here to say, as someone actively working on analyzers for Microsoft, that they are not deprecated. Just trying to understand what was said to give this impression out there in the blog-o-sphere.

[TwoRedCells]

Understandable, more often than not in practice I notice that warnings (such as [Obsolete]) go ignored by developers as they just consider it “noise”.

Good point. That’s part of the issue I’m trying to address. Attributes subclassing [CompilerErrorAttribute] simply would not compile. Warnings of course could be ignored (at their peril). I’m one of those jerks who forces my programmers in submission by checking Treat errors as warnings, and enabling XML comments. 😃