Breakpoint Not Being Hit: "Source Code Is Different"...but it's not

Question

Breakpoint Not Being Hit: "Source Code Is Different"...but it's not

Mark Olbert 6

I am debugging a C# (NET5) WPF app built under the latest non-preview VS 2019. Sometimes I need to attach a separate instance of VS' debugger to the process WpfSurface.com in order to debug design-time problems.

This works reasonably reliably on my desktop system, in that I can set breakpoints as usual, step through code, etc., in the second instance of VS.

But on my Surface Pro 6 (also running the latest non-preview VS 2019) it's wonky. Occasionally that second instance warns me I can't hit a breakpoint because "the source code may be different". It then offers advice on how I can let the breakpoint be hit by changing settings (that help doesn't work, BTW -- they're still not hit).

What confuses me is the file I want to set a breakpoint in is >>exactly<< the same file as I'm editing in the other/primary VS 2019 instance. I've compiled the project so I know there are no unsaved changes.

So why is the second instance of VS2019 warning me about potential differences? Is it looking at a cached version? If so, how do I tell the second instance to clear the cache and reload the actual file? I've tried closing that second instance of VS and re-opening it but that doesn't seem to fix the problem.

Again, this is something I run into frequently on my Surface Pro 6 but rarely, if ever, on my desktop...which is really, really puzzling since they both run the same versions of Windows and VS 2019.

2 answers

Your answer

Answer 1

Tianyu Sun-MSFT 34,436 Microsoft External Staff

Hello @Mark Olbert ,

Welcome to Microsoft Q&A forum.

Perhaps you can try this method: Close every VS instances and go to project/solution folder and delete the .vs, bin and obj folder. Then open VS and open your project Clean > Rebuild it, then debug again.

Feel free to let me know if it works.

Best Regards,
Tianyu

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Mark Olbert 6 Reputation points

2021-06-30T15:14:29.913+00:00

Thanx, Tianyu. But that's not a useful answer for me as it's way too involved to have to go through, multiple times, when I'm trying to debug something on-the-fly.

If a process like you've outlined really is required it points to a bug in Visual Studio, which hopefully Microsoft will get around to fixing.
Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff

2021-07-01T09:21:06.503+00:00

Hi @Mark Olbert , thanks for your reply.

I understand what you mean, yes, I agree with you. It’s indeed could be a potential issue, just one thing to confirm, did you perform the same/almost same operations(add breakpoints, press XXX button, debug… on Surface Pro 6) on your desktop system?

If yes, I suggest you directly report this issue to Visual Studio Product Team on our Developer Community(DC) by clicking Help(in VS) > Send Feedback > Report a Problem… If you do report this issue, please kindly share the thread(DC) link here, and other forum members who meet the similar/same issues will go to vote for the thread. There, VS Product Team will help to fix it if this is a potential issue.

Best Regards,
Tianyu

Answer 2

Duane Arnold 3,216

Did you try a Clean and Build?

Share via

Breakpoint Not Being Hit: "Source Code Is Different"...but it's not

2 answers

Your answer