0

I have had this occur periodically. Once it does, it doesn't seem to go away and I have not been able to figure out why. It is a productivity killer.

I get the message: "Breakpoint will not currently be hit. Unbound Breakpoint."

And the breakpoint does not work.

In trying to research and debug, I have looked at debug/modules. This is a WebAssembly solution and I have noticed that the modules for both the Shared and Server projects are in modules, but the client is not. Should it be there?

My breakpoints work when set in the server project. They also work in the shared project when called from the server project, but not when called from the client.

I have deleted pdb files, cleaned, rebuilt, and re-booted. Nothing helps. Breakpoints are sill displaying as "unbound".

Prv
  • 137
  • 10
  • 1.5 years ago I had a similar problem and received feedback on SO that solved it: https://stackoverflow.com/questions/70659915/stopped-breaking-at-breakpoints-in-blazor-webassembly-client-app-vs2022/70671083#70671083 This is not helping as the inspectUri is already set. I do not see any differences in the LaunchSettings from how it looked a few days ago when breakpoints were working. – Prv Jul 06 '23 at 17:12
  • An update. I had recently upgraded my DevExpress Blazor components. So i restored to prior to that and tested, then re-upgraded and tested again. My results have changed a bit, not sure how or if this could be related. Before: The breakpoints indicated they would not be hit as referenced above. Now: That indicator is gone. Most of the time, the breakpoints will not be hit but occasinally they will. I have not been able to figure out why. The code that I have it set on retrieves the data for my form, so I know it is aways executed even if the breakpoint doesn't fire. – Prv Jul 07 '23 at 15:42
  • Also. I am not getting any responses on Stack Overflow. Does anybody have a suggestion on a forum that might be a better fit for this issue? – Prv Jul 07 '23 at 15:50
  • An update: I found that by deleting the vs, obj, and bin folders I am able to restart breakpoints. However, I am finding that I need to do this multiple times a day - any suggestions on why or how to fix this? In some cases I am simply deleting a breakpoint and adding another. – Prv Jul 13 '23 at 20:47
  • One more update. finding that frequently, deleting the vs, bin , and object folders does not correct the issue. In these cases, so far, they will eventually start working again. However, they have currently not worked in the last 24 hours despite deleting vs, bin, obj repeatedly, deleting the ms Edge cache, and re-starting both the application and my laptop repeatedly. Any suggestions including those on another forum are appreciated. – Prv Jul 15 '23 at 16:07
  • I case this provides insight. In the minutes since my last post, I added a breakpoint on the server in a WebApi and re-tested. That is the only change. Not only did it work, but the breakpoints in the client that had been failing started working again. Sadly, I am expecting that later today the client side breakpoints will again stop working. Any thoughts? – Prv Jul 15 '23 at 16:23

0 Answers0