-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Comments
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. |
@lewing FYI |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis issue has been moved from a ticket on Developer Community. [severity:It's more difficult to complete my work] 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 CommentsFeedback 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)
|
@thaystg Could you please check if this works now? |
It's probably fixed. |
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)
The text was updated successfully, but these errors were encountered: