Use CustomAttributeData for accessing attributes natively.

[GoogleCodeExporter]

We need the full attribute data to be able to grab arbitrary positional and
named parameter values from native attributes.

Basically, because we can't do these things we end up with an
IAttributeInfo API that only supports certain operations for Attributes vs.
all operations for attributes described from metadata in other ways.

Using CustomAttributeData should be about as fast as using Attribute since
the BCL does that internally anyways.

Original issue reported on code.google.com by jeff.br...@gmail.com on 28 Apr 2008 at 9:16

[GoogleCodeExporter]

So far we have effective workarounds for clients that depend on this behavior 
such as
xUnit.Net.

In the long run, we can't really use CustomAttributeData for everything because 
we'll
be missing out on the optimized BCL code paths.  Also I'm not sure if CAD 
reflects on
pseudo custom attributes and security descriptors.

So if we did this, we'd want to define some kind of "option" for retrieving
attributes either fast or complete.  Which means more states and more 
complexity.  Ugh.

Original comment by jeff.br...@gmail.com on 29 Jul 2008 at 2:41

• Added labels: Milestone-3.1, Priority-Low
• Removed labels: Milestone-3.0-a4, Priority-Medium

[GoogleCodeExporter]

Original comment by jeff.br...@gmail.com on 29 Jun 2009 at 8:32

• Added labels: Milestone-3.3

[GoogleCodeExporter]

Original comment by Yann.Tre...@gmail.com on 14 Jun 2011 at 5:53

• Added labels: Milestone-IdeaPool