Mono WASM debugger displays private members of base class alongside other properties

[captainsafia]

Description

When debugging a Blazor WASM application on .NET 5 RC2, I noticed that the debugger populates the locals inspector with private properties from the ComponentBase base class.

The extraneous values displayed are private book-keeping properties used by Blazor's base component class (ref). The class is defined as a public abstract class.

Configuration

• .NET 5 RC 2 (5.0.0-rc.2.20475.17)
• Windows 10
• Visual Studio 16.8 Preview 3

Regression?

This looks like a regression from 3.2. Setting a breakpoint at the same point in a 3.2 app does not surface the issue.

Other information

1. Install the above version of the SDK.
2. Create a new Blazor WASM project with .NET 5 in VS's project creation view.
3. Click F5.
4. Set a breakpoint in the IncrementCount method in the Counter.razor page and observe the issue.

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

[captainsafia]

Update: It looks like we just need to make sure the UX displays them under "Non-public members" as in the example below (Blazor Server app).

[danroth27]

Yeah, in general I think being able to see non-public members is desirable new functionality, but maybe we can do something to improve the UX.

[thaystg]

Okay, the problem here is:
With Just My Code enabled, the private members from inherited classes which are not user classes, are showed inside the non-public-members.
With Just My Code disabled, the private members from inherited classes which are or are not user classes, are showed in the same way as public members.
Imagining that Just My Code is enabled and I have this information as it's expected on #42816, we can try to send the private properties from a non user class in privateProperties array, but this is experimental, or we could just don't send, what do you prefer, @lewing ?

[lewing]

I think we should stick with the current code for net5.0 but we are in urgent need of a way to communicate settings to the proxy.

[lewing]

@thaystg Is this also a VS settings issue? Maybe we should create a tracking issue.