Reputation: 57907
In some sufficiently large applications, you can spend more time figuring out how to drill down to the various layers than you do actually debugging: That's the case with a piece of software I work on now. Layout/separation of concerns issues aside, it'd be nice to have a breakpoint plug-in that would allow you to load breakpoints depending on which Bugzilla/Jira/Fogbugz/SVN defect entry you're working off of.
Do any plug-ins exist for Visual Studio that allow you to 'save' toggled breakpoints to a file, allowing you to load various breakpoints depending on what bug you're working on?
As an adjunct to that question; if there aren't any such plug-ins, can anyone point me to a 'good' (quite a subjective term, but in this case I mean explanatory and useful) resource on creating plug-ins for Visual Studio?
Upvotes: 17
Views: 2358
Reputation: 109170
How about this: "Debugger Settings Visual Studio Add In– Easily Copy Breakpoints between Machines"?
Upvotes: 5
Reputation: 154
I stumbled upon this while searching the web for an answer. Since this question is pretty old, I thought I would contribute with an updated answer.
Nowadays, you can actually import and export breakpoints in Visual Studio from the Breakpoints window (ctrl
+ alt
+ b
)
https://msdn.microsoft.com/en-us/library/dd293657(v=vs.100).aspx
Upvotes: 0
Reputation: 57907
I found this based on a recent Google search:
Breakpoint Workspaces by Rick Schott.
Upvotes: 3
Reputation: 1891
It seems that Visual Studio 2010 (Professional) has added an "export breakpoints to file" function. (You can find it in the Breakpoints window.)
Upvotes: 5
Reputation: 9576
Break point analyzer is a really useful tool for debugging huge projects.
Upvotes: 1