Can't Inspect Static Class Variables in a Blazor Wasm App Using the Debugger

[CincySteve]

I am not able to inspect properties and fields in static classes using the VS Community 2019 v16.8.2 debugger with an AspNetCore 5.0 Blazor Wasm app running on Chrome 86.0.4240.198. I have to assign them to local variables to be able to inspect the values. I have a small repro app that will show the problem, but it seems any app with a static class containing public properties/fields will do.

I think this might be related to #42057, which encompassed an issue I submitted (#40245) plus one before that.

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I am not able to inspect properties and fields in static classes using the VS Community 2019 v16.8.2 debugger with an AspNetCore 5.0 Blazor Wasm app running on Chrome 86.0.4240.198. I have to assign them to local variables to be able to inspect the values. I have a small repro app that will show the problem, but it seems any app with a static class containing public properties/fields will do.

I think this might be related to #42057, which encompassed an issue I submitted (#40245) plus one before that.

Author:	CincySteve
Assignees:	-
Labels:	area-Debugger-mono, untriaged
Milestone:	-

[mkArtakMSFT]

@lewing not sure whether this is a dupe of an existing issue or not.

[lewing]

@radical can you take a look

[CincySteve]

I'm hoping the 6.0.0 milestone (November, 2021) is only a preliminary target. This problem is a big productivity drain, and one I was hoping would have been fixed in the 5.0.0 release that addressed what appears to have been similar problems (#42057) as noted above.

[radical]

I should have a fix for this in a few weeks.

[CincySteve]

@radical That would be great. I can't wait.

[radical]

@lewing Do we know if we should add any extra information to the response to allow the debugger to treat these as static members? I didn't see anything in CDP that might help. I'll surface them same as other members, for now.

[CincySteve]

Just upgraded VS to v16.8.4 and confirmed that I am still experiencing this issue. @radical Any news?