Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
CincySteve opened this issue Nov 22, 2020 · 10 comments · Fixed by #56740
Closed

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

CincySteve opened this issue Nov 22, 2020 · 10 comments · Fixed by #56740
Assignees
@thaystg
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Milestone
6.0.0

Comments

@CincySteve
Copy link

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.
@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/aspnetcore Nov 23, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Debugger-mono untriaged New issue has not been triaged by the area owner labels Nov 23, 2020
@ghost
Copy link

ghost commented Nov 23, 2020

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
Copy link
Member

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

@lewing lewing added this to the 6.0.0 milestone Nov 23, 2020
@lewing
Copy link
Member

lewing commented Nov 23, 2020

@radical can you take a look

@lewing lewing added arch-wasm WebAssembly architecture and removed untriaged New issue has not been triaged by the area owner labels Nov 23, 2020
@CincySteve
Copy link
Author

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
Copy link
Member

radical commented Dec 1, 2020

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

@CincySteve
Copy link
Author

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

@radical
Copy link
Member

radical commented Dec 8, 2020

@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
Copy link
Author

CincySteve commented Jan 17, 2021 •
edited
Loading

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

@radical radical mentioned this issue Mar 10, 2021
Merged
@radical
Copy link
Member

radical commented Jul 29, 2021

@thaystg is this fixed with main?

@thaystg
Copy link
Member

thaystg commented Jul 30, 2021

No.

@thaystg thaystg self-assigned this Jul 30, 2021
@radical radical removed their assignment Aug 1, 2021
@thaystg thaystg mentioned this issue Aug 2, 2021
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Aug 2, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Aug 3, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Sep 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@thaystg thaystg

Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Projects
None yet
Milestone
6.0.0
Development

Successfully merging a pull request may close this issue.

[wasm][debugger] Inspect static class thaystg/runtime
6 participants
@radical @lewing @thaystg @CincySteve @mkArtakMSFT @Dotnet-GitSync-Bot