Share via

What File Has My Breakpoint Information?

a_unique_name 421 Reputation points
2026-03-01T03:54:14.81+00:00

Developing C++ code.

I try to keep my backup files small by removing directories like .vs.

One thing I miss when recovering a project (solution) is the breakpoints, which can be elaborate.

Is there a particular file that contains a project's breakpoints that I can save with the other files I use to recover a project?

Thanks
Larry

Developer technologies | Visual Studio | Debugging
0 comments No comments
{count} votes

Answer accepted by question author
  1. RLWA32 52,256 Reputation points
    2026-03-01T10:26:59.9033333+00:00

    Larry,

    In my experience Visual Studio stores breakpoints for C++ projects in the hidden .suo file for the solution.

    For example, following shows a VS2022 solution containing two C++ projects each of which has a beakpoint set.

    BPTestInitial

    Then I closed the solution, and exited VS. I deleted the FileContentIndex folder created by VS under the hidden <SolutionDir>.vs folder and everything except for the .suo file under the <SolutionDir>.vs\V17 folder.

    Then I moved the .suo file to a different file system location from which it could be restored.

    I started VS and opened the solution. Following is what was displayed -

    BPTestNew

    Note that the breakpoints are gone and there are no opened source files.

    I closed the solution, exited VS and cleaned the the solution's folders as above. Except this time I deleted the newly created .suo file and restored the initial file from where it had been saved.

    Start VS and open the solution --

    BPTestRestored

    Breakpoints have been restored as well as the open files.

    3 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-01T03:54:25.4366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Visual Studio does not store C++ source-code breakpoints in a single simple file inside the solution that can be backed up separately. Instead, breakpoints are part of the Visual Studio debugger state and can be managed and persisted using the Breakpoints window and its export/import feature.

    To preserve and restore breakpoints across machines or after deleting .vs and other local state, export them before cleaning up and re-import them later:

    1. Open the Breakpoints window: Debug > Windows > Breakpoints (or press Ctrl+Alt+B).
    2. To export:
      • To export a single breakpoint, right-click it in the source code or Breakpoints window and select Export (or Export selected), then choose a location and Save.
      • To export several breakpoints, in the Breakpoints window select the checkboxes for the desired breakpoints or filter them via the Search box, then select the Export all breakpoints matching the current search criteria icon and save the XML file.
      • To export all breakpoints, clear all checkboxes and leave Search empty, then select the same Export all breakpoints matching the current search criteria icon and save.
    3. Keep the resulting XML file with the other project backup files.
    4. After restoring or moving the project, open the Breakpoints window again and select the Import breakpoints from a file icon, choose the saved XML file, and open it. The breakpoints (and, in newer Visual Studio versions, breakpoint groups) are restored.

    This XML file is the portable artifact that can be backed up and moved between environments; there is no need to track an internal Visual Studio state file.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.