CallerMemberNameAttribute is not filled - by Harry-vB

Status : 


Sign in
to vote
ID 776904 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 1/18/2013 7:56:59 AM
Access Restriction Public


Under some circumstances an overload for a method using the CallerMemberNameAttribute confuses the compiler.
Sign in to post a comment.
Posted by Bill [MSFT] on 4/12/2013 at 2:52 PM
Hi. The VB late binder does not pass the caller's name. Since it doesn't know if it would be calling something that takes the caller's name, VB choses not to store the name for every method in case it late binds to a callee that takes it.

Posted by Macy [MSFT] on 1/20/2013 at 9:37 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 1/18/2013 at 8:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(