You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a type/method that I've added [deprecated("foo", deprecate, 1)] to.
ca.GetArguments(outvarfixedArgs,outvarnamedArgs);
both argument lists are empty, because it's trying to resolve the custom attribute in the same Assembly where it is applied to.
The code correctly identifies the need to resolve DeprecationType in the Windows.FoundationContract assembly, but this is marked as a fake assembly, so it calls RaiseFakeTypeRequired, but the FakeTypeRequired event handler is null.
Attributes outside of the target assembly should be OK, but I don't think there's a way to make this work with a fake type. At least when there's an enum involved, it's necessary to know the type information so that the metadata reader understands the binary layout in the file.
(Error shows up here, fallback code for attributes is here).
I have a type/method that I've added
[deprecated("foo", deprecate, 1)]
to.both argument lists are empty, because it's trying to resolve the custom attribute in the same
Assembly
where it is applied to.The code correctly identifies the need to resolve
DeprecationType
in theWindows.FoundationContract
assembly, but this is marked as a fake assembly, so it callsRaiseFakeTypeRequired
, but theFakeTypeRequired
event handler is null.Update:
The solution is to do something like:
This should probably be a default though, or at least documented :)
The text was updated successfully, but these errors were encountered: