Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Hide some generated Razor page properties in the debugger
See original GitHub issueWe’re improving the ASP.NET Core debugging experience. One area that can improve is debugging Razor pages.
A generated Razor pages add some properties:
These don’t provide useful information in the debugger and clutter the debug view for the page. We want to limit the debug view to useful information such as the page model, properties added to the page by the developer, and request information.
Because this properties are added in generated pages, the Razor page generator needs to place [DebuggerBrowsable(DebuggerBrowsableState.Never)] on the properties.
These should be hidden in Razor pages and MVC views.
Issue Analytics
- State:
- Created 2 months ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Don’t think this is the best approach. While not useful in most scenarios I’m sure that certain segments of customers do find them useful. This property effectively hides them in all cases.
I don’t think there is a good way to do this. Closing for now.