Options
DebuggerDisplay attribute
Is it intentional that LINQPad ignores the DebuggerDisplay attribute? (tested on v5.22.02 Any CPU)
obviously I wouldn't expect it to affect the "Dump" method, but i.e. example (from https://msdn.microsoft.com/en-us/library/x810d419.aspx): http://share.linqpad.net/njlbne.linq - if one was to put a breakpoint on
(I'm just adding a cross-link here to http://forum.linqpad.net/discussion/comment/2915/#Comment_2915, where I know we had a bit of a discussion about how the debugger works, using func-eval, in case others will find it interesting.)
obviously I wouldn't expect it to affect the "Dump" method, but i.e. example (from https://msdn.microsoft.com/en-us/library/x810d419.aspx): http://share.linqpad.net/njlbne.linq - if one was to put a breakpoint on
mc.Dump(); and a watch on mc, I'd expect the Value in the Watch tab and the Locals tab to show 6 instead of UserQuery+MyClass.(I'm just adding a cross-link here to http://forum.linqpad.net/discussion/comment/2915/#Comment_2915, where I know we had a bit of a discussion about how the debugger works, using func-eval, in case others will find it interesting.)
Comments