Advise for debugging
-
Debuggin for me is a pain in the $ss. What sofisticated methods are there to debug programs easier. (Ie: something else then : Put breakpoints and press F11). There is a way of using trace, and logging also helps, but what else is there. Good practices are also welcome. (By the way i have already read The Standalone Programmer Series.)
-
Debuggin for me is a pain in the $ss. What sofisticated methods are there to debug programs easier. (Ie: something else then : Put breakpoints and press F11). There is a way of using trace, and logging also helps, but what else is there. Good practices are also welcome. (By the way i have already read The Standalone Programmer Series.)
HAHAHA_NEXT wrote: Debuggin for me is a pain in the $ss Are you a programmer? :wtf: Well, you can use some class like
TraceorDebugwhich have some methods to write information you want in a file,event viewer or output window. Mazy "A bank is a place that will lend you money if you can prove that you don't need it." - Bob Hope -
HAHAHA_NEXT wrote: Debuggin for me is a pain in the $ss Are you a programmer? :wtf: Well, you can use some class like
TraceorDebugwhich have some methods to write information you want in a file,event viewer or output window. Mazy "A bank is a place that will lend you money if you can prove that you don't need it." - Bob HopeMazdak wrote: Are you a programmer? Sheesh, no kidding! This is part of the trade. Get used to it!
TraceandDebugwith the default and customTraceListenerimplementations can tell you some things, but it's not even CLOSE to what properly debugging your app and checking the state of variables throughout your object and related objects can tell you.Microsoft MVP, Visual C# My Articles
-
Mazdak wrote: Are you a programmer? Sheesh, no kidding! This is part of the trade. Get used to it!
TraceandDebugwith the default and customTraceListenerimplementations can tell you some things, but it's not even CLOSE to what properly debugging your app and checking the state of variables throughout your object and related objects can tell you.Microsoft MVP, Visual C# My Articles
Heath Stewart wrote: but it's not even CLOSE to what properly debugging your app and checking the state of variables throughout your object and related objects can tell you Yah, but I thought it could be ease some of his pain in *ss. :-D ;) Mazy "A bank is a place that will lend you money if you can prove that you don't need it." - Bob Hope
-
Heath Stewart wrote: but it's not even CLOSE to what properly debugging your app and checking the state of variables throughout your object and related objects can tell you Yah, but I thought it could be ease some of his pain in *ss. :-D ;) Mazy "A bank is a place that will lend you money if you can prove that you don't need it." - Bob Hope
but it's not even CLOSE to what properly debugging your app and checking the state of variables throughout your object and related objects can tell you 1) This i know, but this is the slowest way of doing things, and works well when you can test a small part of your program. 2) As experienced programmers you must have other tricks then that. For example, i put a comment //WORKS on the part which works, so not checking it. Believeing that there is no more tricks, is like beliving that 2 + 2 is the only thing they teach us in math.
-
Debuggin for me is a pain in the $ss. What sofisticated methods are there to debug programs easier. (Ie: something else then : Put breakpoints and press F11). There is a way of using trace, and logging also helps, but what else is there. Good practices are also welcome. (By the way i have already read The Standalone Programmer Series.)
I believe someone wants a
System.Diagnostics.FixItclass. :-) Debugger tools are like any other tool: A hammer drives nails and it can help build a house but it doesn't do that for you automatically. I could tell you how to use the VS.Net Debugger but you'll never gleen the useful tactics and tricks to spot errors easily without actually doing it yourself. The .Net SDK comes with a debugger...its functional but lacks bells and whistles. The debugger in VS.Net works well enough. But it just spits out data for you to figure out. The rest is up to you to figure out. For general debugging behavior you should look atSystem.Diagnostics.DebuggerandSystem.Diagnostics.Debug(or heck theSystem.Diagnostcisnamespace).