Debug points are not getting hit in VS2019

Antriksh Kakkar 0

I am using visual c++ and have multiple dlls in my solution. When i change 1/2 files and build that dll then all breakpoints added in other files of that dll does not hit.

To fix this I need to rebuild that dll again which is quite time consuming.

Can you please suggest how to overcome this issue?

I have VS2015 installed too and I have never faced this issue in VS2015.

Tianyu Sun-MSFT 30,356 Reputation points Microsoft Vendor

2023-05-22T09:56:42.26+00:00

Hello @Antriksh Kakkar ,

Welcome to Microsoft Q&A forum.

I failed to reproduce this issue. If this issue is reproducible, could you please share us detailed steps/sample code snippets to reproduce this issue and check further?
Antriksh Kakkar 0 Reputation points

2023-05-22T19:23:09.32+00:00

Hi @Tianyu Sun-MSFT ,

Sorry but i can not share code snippets with you.

Steps are very simple. I Have a solution which contains more than 50 projects. When I Clean build any of the project every breakpoint in every file of the project hits. But as soon as I change some code in any file(e.x. xyz.cpp)of that project and do build only then breakpoint of edited file hits(xyz.cpp) but all other breakpoints applied in other files of this project shows:

Again when i rebuild the the project then all breakpoints starts hitting again.

Thanks

Antriksh
Tianyu Sun-MSFT 30,356 Reputation points Microsoft Vendor

2023-05-29T14:07:17.81+00:00

Hi Antriksh,

Does removing the hidden .vs folder in your solution folder and renaming ComponentModelCache folders in this directory: C:\Users\username\AppData\Local\Microsoft\VisualStudio\17.0_XXXXXXXX\ work? Can you confirm that if this issue is reproducible in a newly created solution/project?
Antriksh Kakkar 0 Reputation points

2023-05-30T12:05:04.16+00:00

Removing hidden .vs folder doesn't helped.

I don't have any 17.0_XXXXXXXX folder at the mentioned location instead i have 16.0_XXXXXXXX folder. Shall I rename it? If yes, Is there any specifc name to be given to 16.0_XXXXXXXX folder?
Tianyu Sun-MSFT 30,356 Reputation points Microsoft Vendor

2023-05-31T05:42:09.3333333+00:00

Hi @Antriksh Kakkar ,

Yes, I’m sorry, 17.0 is for VS 2022, 16.0 is for VS 2019, you need to rename 16.0_XXXXXXXX folders. The name is specific but the eight characters are randomly generated, you need to rename all the 15.0_XXXXXXXX folders.
Antriksh Kakkar 0 Reputation points

2023-05-31T06:22:39.98+00:00
Hi @Tianyu Sun-MSFT

Sorry I got confused.

Do I need to rename 16.0_XXXXXXXX folders or 15.0_XXXXXXXX or both?

What should be the new name?
Tianyu Sun-MSFT 30,356 Reputation points Microsoft Vendor

2023-05-31T09:02:43.8966667+00:00

Hi @Antriksh Kakkar ,

Renaming 16.0_XXXXXXXX folders is enough, as the issue only appears in VS 2019(VS 2022-17, VS 2019-16, VS 2017-15, VS 2015-14...).

Actually the purpose is to remove those folders, renaming does the same, but safer and quicker. So any new name is correct.
Antriksh Kakkar 0 Reputation points

2023-06-04T14:16:35.6066667+00:00

Renaming the folder doesn't fix the issue.

Share via

Debug points are not getting hit in VS2019

Your answer