Visual studio and .NET tip 12:- Pin debugging and commenting
By Shivprasad Koirala
INSTANTLY dtSearch TERABYTES OF POPULAR DATA TYPES; hundreds of reviews, etc.!
Many times while debugging we would like to:-
• See the debugged value after debugging has finished.
• Enter comments while debugging and see these comments later.
• Pin the debugger so that we can see the values while debugging.
Many times as a developer you come across functions with lots of input parameters as shown in the below code snippets. In real projects the input parameters would be much higher as compared to the below code snippets. Some times for various reasons you want to shuffle them, reorder them or remove some of them.
We all know exceptions get propagated from the last caller to the main caller. For instance let’s say from your static void main method you are calling “SomeMethod” and he in turn is calling “SomeMethod1”.
While debugging you often want to skip debugging on certain lines of code. For instance in the below code you have set the debug point to the first line, you would like to skip the in between lines and jump directly to “console.writeline” step.
In big project you have 100’s of classes and each of those classes can have lots of properties.
As developer debugging is your routine job and you would like your debugger to debug smartly rather than monotonously. For instance in the below code we have put a debug point and we do not want our debugger to just break monotonously.
As a developer you always need some common codes again and again. Rather than writing those common codes from scratch you would like to get them easily from some handy place.
Visual studio and .NET tip 12:- Pin debugging and commenting (1251 Views)