Visual Studio 2010 SP1 beta allows you to save IntelliTrace information from IntelliTrace Window. During debugging you may found, the current debugging information is important for you and it’s needs to be save and you don’t want restart the debug session. For this type of situation now you can save log information from IntelliTrace window itself. From Visual… Read More »
When debugger hits the breakpoint, if you mouse over to any of the objects or variables, you can see their current values in the DataTip. This helps us for debugging Even you can get the details of some complex object like dataset, datatable, etc. There is a “+” sign associated with the dataTip which is used to expand… Read More »
Use code>DebuggerBrowsable attribute to customize the debugging windows Use DebuggerDisplay attribute to customize the debugging display.
By Marking a piece of code using DebuggerStepThrough attribute tells the Visual Studio debugger that, the code block will be stepped over from debugging process. you can mark methods, properties with DebuggerStepThrough attributes where you don’t want to stop your code to break. If there is any break point inside a code section which is marked as “DebuggerStepThrough”… Read More »
DubuggerHidden attribute tells the Visual Studio debugger that the method is hidden from the debugging process and while debugging. This is quite helpful when you don’t want to go to stepping inside of a method while debugging. When you mark a method with DebuggerHidden() attributes, It’s explicitly tells the debugger not to step inside of that methods and… Read More »
In this post I have explained how you can use Obsolete attributes to mark some methods which are not no longer in used or may be remove in future release of the class. During the development cycle we may need to change the name or declaration of certain methods which may be using by some other developers. In… Read More »
Sometimes during development you may need to avoid the unnecessary compiler warnings to show in warning window. Though it’s not recommended to suppress the warning explicitly, but during some debugging and analysis of code you may want to hide them for time being. In this post I have explained how you can hide the unwanted warning explicitly by… Read More »
During debugging in visual studio we generally used watch window to explore the objects, values, properties and other nested objects as a tree structure. Most of the time we used watch window to only view the values or change the current object properties values to see the effects of changed object during debugging. And most of the time… Read More »