To avoid old-fashioned non-generic syntax when searching for attributes of a known type, one usually uses the extension methods in System.Reflection.CustomAttributeExtensions
class (since .NET 4.5).
However this appears to fail if you search for an attribute on the return parameter of an overridden method (or an accessor of an overridden property/indexer).
I am experiencing this with .NET 4.6.1.
Simple reproduction (complete):
using System;
using System.Reflection;
namespace ReflectionTrouble
{
class B
{
//[return: MyMark("In base class")] // uncommenting does not help
public virtual int M() => 0;
}
class C : B
{
[return: MyMark("In inheriting class")] // commenting away attribute does not help
public override int M() => -1;
}
[AttributeUsage(AttributeTargets.ReturnValue, AllowMultiple = false, Inherited = false)] // commenting away AttributeUsage does not help
sealed class MyMarkAttribute : Attribute
{
public string Descr { get; }
public MyMarkAttribute(string descr)
{
Descr = descr;
}
public override string ToString() => $"MyMark({Descr})";
}
static class Program
{
static void Main()
{
var derivedReturnVal = typeof(C).GetMethod("M").ReturnParameter;
// usual new generic syntax (extension method in System.Refelction namespace):
var attr = derivedReturnVal.GetCustomAttribute<MyMarkAttribute>(); // BLOWS UP HERE, System.IndexOutOfRangeException: Index was outside the bounds of the array.
Console.WriteLine(attr);
// old non-generic syntax without extension method works:
var attr2 = ((MyMarkAttribute[])(derivedReturnVal.GetCustomAttributes(typeof(MyMarkAttribute), false)))[0]; // OK
Console.WriteLine(attr2);
}
}
}
The code may look "too long to read", but it is really just an overridden method with an attribute on its return parameter and the obvious attempt to retrieve that attribute instance.
Stack trace:
Unhandled Exception: System.IndexOutOfRangeException: Index was outside the bounds of the array. at System.Attribute.GetParentDefinition(ParameterInfo param) at System.Attribute.InternalParamGetCustomAttributes(ParameterInfo param, Type type, Boolean inherit) at System.Attribute.GetCustomAttributes(ParameterInfo element, Type attributeType, Boolean inherit) at System.Attribute.GetCustomAttribute(ParameterInfo element, Type attributeType, Boolean inherit) at System.Reflection.CustomAttributeExtensions.GetCustomAttribute[T](ParameterInfo element) at ReflectionTrouble.Program.Main() in c:\MyPath\Program.cs:line 38
Am I doing anything obviously wrong?
Is this a bug, and if yes, is it well-known, and is it an old bug?
This indeed looks like a bug. The problem seems to be with the inheritance. This does work:
ReturnParameter.GetCustomAttribute<MyMark>(inherit: false)
Retrieving attributes have two code paths that work a bit differently: MemberInfo.GetCustomAttribute
(older) and Attribute.GetCustomAttribute
(newer and recommended). There are also the generic extension methods, which use the latter, newer approach. The difference between these is indeed the way they handle inheritance. .NET 1.0 ignored the inherit
parameter for properties, events and parameters. So in order not to break things, the static methods on Attribute
we introduced in .NET 2.0 (together with this bug).
Seems like they neglected to special-case the return value parameter when going up the inheritance tree (see here). You can open an issue in the GitHub repo or a Connect bug.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With