While dealing with IntelliTrace, sometime you must have noticed there are so many event capture by the IntelliTrace. You can filter them out by selecting categories from IntelliTrace Window which will minimize the number of events captured. As shown in below image, I have filtered the records on “ASP.NET” Categories,hence it’s displaying all the ASP.NET Related events. But… Read More »
If you are dealing with any objects in Watch window and you want to check the current generation for that Object you can easily get that by calling GC.getGeneration(objectName). If you are creating any Object ID in Watch window let say (#1), you can also view the generation of the newly created object ID GC.getGeneration(#id)
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 »