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.

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

Unable to see Inherited Properties in Blazor projects #47658

Closed
vsfeedback opened this issue Jan 29, 2021 · 5 comments · Fixed by #56754
Closed

Unable to see Inherited Properties in Blazor projects #47658

vsfeedback opened this issue Jan 29, 2021 · 5 comments · Fixed by #56754
Assignees
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Milestone

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
The blazor project I am working on uses classes with inheritance. When in debug mode, when I hover over a derived class object to look at its properties, visual studio only shows the child properties, it does not show the properties it inherited from the base class. Despite them not being shown, the are in fact there. They can be read from and written to, just not seen in the debugger.

The blazor app is a web assembly client app, not a server. I created separate folders in the project for the Models and Data. The classes are stored in a single file. The content of the classes is irrelevant, the issue arises whether its complex or simple so if youre attempting to recreate, it should suffice to put a single int property in both the base and derived classes. The Data folder contains a service. Debugging the service is where the problem first showed up, but i then found it everywhere. for testing, the service has a single method that is called from the index page. It creates objects of the derived type and has a line with a breakpoint that allows you to view the objects. The index page has a button that calls the method from the service.

Following these steps I have managed to recreate the problem consistently when I create a new project from scratch.

! [debugger properties snapshot.png] (https://aka.ms/dc/image?name=B2991da78d84243b0a56691939b299bc5637472708862029586_debugger_properties_snapshot.png&tid=2991da78d84243b0a56691939b299bc5637472708862029586)


Original Comments

Feedback Bot on 1/26/2021, 06:08 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/aspnetcore Jan 29, 2021
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jan 29, 2021
@mkArtakMSFT
Copy link
Member

@lewing FYI

@lewing lewing added arch-wasm WebAssembly architecture area-Debugger-mono and removed untriaged New issue has not been triaged by the area owner labels Jan 29, 2021
@ghost
Copy link

ghost commented Jan 29, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
The blazor project I am working on uses classes with inheritance. When in debug mode, when I hover over a derived class object to look at its properties, visual studio only shows the child properties, it does not show the properties it inherited from the base class. Despite them not being shown, the are in fact there. They can be read from and written to, just not seen in the debugger.

The blazor app is a web assembly client app, not a server. I created separate folders in the project for the Models and Data. The classes are stored in a single file. The content of the classes is irrelevant, the issue arises whether its complex or simple so if youre attempting to recreate, it should suffice to put a single int property in both the base and derived classes. The Data folder contains a service. Debugging the service is where the problem first showed up, but i then found it everywhere. for testing, the service has a single method that is called from the index page. It creates objects of the derived type and has a line with a breakpoint that allows you to view the objects. The index page has a button that calls the method from the service.

Following these steps I have managed to recreate the problem consistently when I create a new project from scratch.

! [debugger properties snapshot.png] (https://aka.ms/dc/image?name=B2991da78d84243b0a56691939b299bc5637472708862029586_debugger_properties_snapshot.png&tid=2991da78d84243b0a56691939b299bc5637472708862029586)


Original Comments

Feedback Bot on 1/26/2021, 06:08 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

Author: vsfeedback
Assignees: -
Labels:

arch-wasm, area-Debugger-mono

Milestone: -

@lewing lewing added this to the 6.0.0 milestone Jan 29, 2021
@radical
Copy link
Member

radical commented Jul 29, 2021

@thaystg Could you please check if this works now?

@radical radical removed their assignment Jul 29, 2021
@lewing lewing modified the milestones: 6.0.0, 7.0.0 Jul 31, 2021
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Aug 2, 2021
@thaystg
Copy link
Member

thaystg commented Aug 3, 2021

It's probably fixed.

@thaystg thaystg closed this as completed Aug 3, 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.
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants