Create an Attribute to Break the Build

Question

OK, this kind of follows on from my previous question.

What I would really like to do is create some sort of attribute which allows me to decorate a method that will break the build. Much like the Obsolete("reason", true) attribute, but without falsely identifying obsolete code.

To clarify: I dont want it to break the build on ANY F6 (Build) press, I only want it to break the build if a method decorated with the attribute is called somewhere else in the code. Like I said, similar to obsolete, but not the same.

I know I am not alone in this, since other users want to use it for other reasons. I have never created custom attributes before so it is all new to me!

Answer 1

I think this would be an excellent feature request for Microsoft: Create an abstract base class attribute CompilerExecutedAttribute that the compiler processes in some manner or that can influence the compiling process. Then we could inherit from this attribute and implement different operations, e.g. emit an error or a warning.

Answer 2

If this is for XML serialization and NHibernate, where you want the parameterless constructor to be accessible (as is the case in the example you referenced), then use a private or protected parameterless constructor for serialization, or a protected constructor for NHibernate. With the protected version, you are opening yourself up to inherited classes being able to call that code.

If you don't want code calling a method, don't make it accessible.

EDIT: To perhaps answer the deeper question, AFAIK the compiler only knows about three attributes: Obsolete, Conditional, and AttributeUsage. To add special handling for other attributes would require modifying the compiler.

Answer 3

If you consider a warning (which is what [Obsolete] throws up) build-breaking, then just use the #warning compiler directive.

Edit: I've never used it, but #error is also available.

Answer 4

I think the only fool proof way would be to extend the Visual Studio (through VSIP) and subscribe to the correct event (maybe in the EnvDTE.BuildEvents) class, and check your code for usage of the constructor, and cancel the build if you detect it.

Answer 5

Throw a custom exception and unit test for it as a post build step

Answer 6

Responding 4 years later :)

I had same question if there were an alternative to Obsolete.

From what I recall (channel9 videos) a little while ago Microsoft stated that it is working on giving devs access to something like a compiler api at some point so in the future it's conceivable that you could write a compiler "plugin" that would allow to to decorate methods with your own custom attribute and tell the compiler to cancel if it looks like the decorated code could be getting called some where else in the code etc.

Which would actually be pretty cool when you think about it. It also reminds me that I should also try and read up on the progress of that compiler api thing MS is working on ...

Answer 7

This is all starting to sound a bit like Yesterday's TDWTF. :-)

Answer 8

I will have to agree with Greg: make up an attribute for it.

And if you're really serious, maybe find a way to figure out if the constructor is being accessed by anything other than XMLSerializer and throw an exception if it is.

Answer 9

I'd suggest you to use the #error directive.

Another pretty unknown attribute that might do the work is the conditional attribute (depending on what you're trying to ahieve)

[Conditional("CONDITION")] 
public static void MiMethod(int a, string msg)

which will remove the method invocation from the IL code itself if "MY_CONDITION" is defined.

Answer 10

Create an FxCop rule, and add FxCop to your integration build in order to check for this.

You'll get warnings, rather than a failing build. Attributes 'run' at reflection time rather than build time.

Alternatively (and this is rather nasty) put a compiler directive around the method you don't want to be called. Then your code will break if you call it, but you can set up a build that passes the right compiler directive and doesn't.

Answer 11

Why not just make something up? An unknown attribute would surely break the build.

[MyMadeUpAttributeThatBreaksTheBuildForSure]
public class NotDoneYet {}