Option to Separate Breakpoints from Source Code

[_carl]

Breakpoints are great for debugging.  But...I've never wanted to share them with another developer, and I've never liked it when they add the dirty dot to code that I haven't otherwise changed.  This can lead to unnecessary code changes which can add hassle to source control, and it can lead to other developers unintentionally inheriting your debugging breakpoints.

How about an option to manage breakpoints separately from source code, perhaps similar to how compiled code is handled?

[thols]

My last team hated when I checked in code with breakpoints added. I thought of adding a pre-commit hook to look for breakpoints before allowing commit to SCC but never got to it. I would have liked this feature. Now I'm a single developer and don't need it, but it would still be good to be able to separate breakpoint change from real code change.

[AristosQueue (NI)]

Duplicate idea:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Savable-Probe-Sets-and-Breakpoint-Sets/idi-p/1015858

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Breakpoints-should-not-be-stored-in-VIs/idi-p/1954585