Restrict custom attribute to property by type

Question

0.00/5 (No votes)

See more:

I am writing a custom attribute. I have applied the AttributeUsage attribute to it, restricting its use to properties only. This works fine: trying to use the attribute on a class or method results in a design-time error, which is exactly what I want.

I would like to restrict it further, so it can be used only on properties that return a String. That is to say, it will result in a design-time error if applied to a DateTime or other non-string. Is this kind of precision possible and, if so, how would I do it?

Posted 25-Jun-12 7:06am

Gregory Gadow

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2012-06-25T07:36:00

Not supported. It doesn't get any more granular than down to a Property. You cannot restrict it to a return type of a property.

There is no way to do this at runtime inside the attribute code either. The attribute doesn't know anything about the item it's been attached to. It only adds metadata to the item.

The only way I know of that can enforce proper usage would be code written in Unit Tests to Refelect the type and make the determination and/or a custom written FxCop rule.