You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some nice Assert methods to simplify assertion but it would also
be nice to specify breakpoints in a similar manner for use when debugging
problems. It would certainly be easier than adding conditional breakpoints.
Original issue reported on code.google.com by jeffma...@gmail.com on 10 Mar 2009 at 10:11
The text was updated successfully, but these errors were encountered:
I realise this is slightly (okay, maybe grossly) outside the intentions of this
project but it just seems like such a nice simple method to add that could aid
in the
debugging of some rather annoying collection problems that would otherwise
require
some stress with the breakpoint condition dialog.
Original comment by jeffma...@gmail.com on 11 Mar 2009 at 9:36
In hindsight, I'm not convinced anymore. I don't know why I didn't consider
it, but
is it really worth going to this effort when all one needs to write is:
from x in myCollection
where MyBreakpointCondition(x)
Debugger.Break()
?
Original comment by jeffma...@gmail.com on 17 Mar 2009 at 3:44
Original issue reported on code.google.com by
jeffma...@gmail.com
on 10 Mar 2009 at 10:11The text was updated successfully, but these errors were encountered: