We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have attached a basic demo app project where I link site.js in App.razor. Steps to reproduce the issue:
I think the problem is that this opens in a new tab and the debugger may not be attached to it.
I do not like the idea of having to set breakpoints only in Dev Tools in the browser.
Can someone help me figure out how to make normal VS2022 breakpoints work in this scenario?
Thank you!
BlazorServerJsBreakpoints.zip
I expect to be able to hit the Javascript breakpoint when it is set in VS2022 in site.js.
No exceptions.
.net 8
.NET Aspire 9.0.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
Describe the bug
I have attached a basic demo app project where I link site.js in App.razor.
Steps to reproduce the issue:
I think the problem is that this opens in a new tab and the debugger may not be attached to it.
I do not like the idea of having to set breakpoints only in Dev Tools in the browser.
Can someone help me figure out how to make normal VS2022 breakpoints work in this scenario?
Thank you!
BlazorServerJsBreakpoints.zip
Expected Behavior
I expect to be able to hit the Javascript breakpoint when it is set in VS2022 in site.js.
Steps To Reproduce
Exceptions (if any)
No exceptions.
.NET Version info
.net 8
Anything else?
.NET Aspire 9.0.0
The text was updated successfully, but these errors were encountered: