It\u2019s a common doing for a developer to devote fine quantum of time in daily activities to debug the code, recognize the actual reason of defect and ultimately find a solution for it. During the process, you might come across few bugs which are easily identified and solved, but some of them are so intricate that they take quite a long time to even come into knowledge of a developer. This leads to a developer spending an excess amount of time on debugging than writing an actual piece of code. <\/p>\n
You must have heard a lot of praises about Visual Studio and thankfully, it gives numerous of tools that slickly and efficiently debug code. Developers mainly go for tools like breakpoints, watch window, process attach window, however, it\u2019s good to be productive and try our other debugging ways that will help in recognizing the bugs promptly, so that it\u2019s timely dealt with. <\/p>\n
Here are the useful tricks and techniques that will help in saving you quite some time while using Visual Studio:<\/p>\n
Use DebuggerHidden feature to hide methods from debugger<\/strong> Correctly use Runtime Objects in Watch Window while debugging<\/strong>
\nThis attribute works wonders as it informs the Visual Studio debugger about the method being hidden from debugging process. This exceptionally comes handy when you want to avoid going deep into method during debugging. <\/p>\n
\nWatch Windows work like a charm while debugging in visual studio as they help in looking at objects, values, properties and other nested objects as a tree structure. Earlier it was used by developers to view values or change current object property values to examine the effects of the changed object during debugging. But Visual Studio works when a brand new object is needed as well. <\/p>\n