Exception Occurred ? – Get Troubleshooting tips from your favorite blogs January 7, 2011
Posted by Abhijit Jana in Tips and Tricks, Visual Studio.Tags: codeproject, Customize Exception Assistant, Exception Handling, Tips, Visual Studio
5 comments
In this blog post, I am going to share a quite interesting tips, where you can customize the “Exception Assistant” in visual studio. I have explained how we can use this features for an custom exception class, where we want to provides custom or additional help information . As an example, I have shown how we can set some favorite blogs urls in troubleshooting tips section.
Video Webcast: 10 Tips you should know about “Watch Window” While debugging in Visual Studio January 3, 2011
Posted by Abhijit Jana in Debugging, Visual Studio.Tags: Debugging, Tips, Visual Studio, watch window
8 comments
Few months back I have published an article on 10 Tips you should know about “Watch Window” While debugging in Visual Studio , where I have explained about 10 useful tips on watch window. Here I am sharing you the quick video webcast on that.
Add document header for files automatically in Visual Studio December 5, 2010
Posted by Abhijit Jana in Tips and Tricks, Visual Studio.Tags: How To, Tips and Tricks, Visual Studio
26 comments
In this blog post I am going to share how you can add a document header 
of xml comments with code file automatically. This is going to be an very interesting and helpful for all of you who are using styleCop to maintain coding standard. Actually extensive using of StyleCop helped me to think to make it automate. There are many tools available which can helps us in this case to do this automatically. But I always prefer let’s Visual studio do the job for me. Here I am going to share with you two different approaches to deal with this issue. Now it’s up to you which one to use.
Tips : “Remove and Sort” Namespaces using Shortcut in Visual Studio December 4, 2010
Posted by Abhijit Jana in Tips and Tricks, Visual Studio.Tags: codeproject, Tips and Tricks, Tools
6 comments
While dealing with maintaining coding standard like stylecop warning fix with code, most of the time we need to remove unused namespaces and sort the namespaces. We can do it easily from the context menu of the code editor. There you have three different option for “Organize Using” . Either you can Remove Unused Usings , Sort Usings or we can do it together by selecting “Remove and Sort” . Let’s see how we can make it more handy !
How to use out of scope object with in Conditional Breakpoint ? December 2, 2010
Posted by Abhijit Jana in Debugging, Tips and Tricks, Visual Studio.Tags: Debugging, How To, Out of Scope Object Debugging, Tips and Tricks
1 comment so far
During debugging of your application, you may need to keep track of some data which are already out of scope. Say, You call a MethodB() from MethodA() and did some operation inside MethodB(), now when you returned back to MethodA(), all the local variables inside MethodB() are
out of scope. But you want to use them in MethodA(). Now here is the trick, that you can create an ObjectID for an member variables or objects and can track the same when it’s out of scope as well, but until GC() does not collect it. In this post, I am going to explore how we can use an Out of Scope object value to deal with Conditional Break points. To start with, first you have to understand how to use Object ID to track and out of scope object. Here is my complete article How to track an object which is Out of Scope while Debugging ? . Though I described a quick look into use of out of scope object inside conditional breakpoints on that article, I received few query about more details on the same. So here I am going to give some more details.
Use Shortcut or Context Menu for “Open Containing Folder” in Visual Studio November 8, 2010
Posted by Abhijit Jana in Tips and Tricks, Visual Studio.Tags: Beginners, codeproject, Tips and Tricks, Visual Studio
6 comments
“Open Containing Folder” is one of the frequent used functionality to open a particular file location in windows explore from Visual Studio IDE . How did we do that ? Yes it’s very simple, Just right click on file from files Tab and select “Open Containing Folder” from the context menu as shown in below.
This will open the selected item location in windows explorer. This operation by default having no keyboard shortcut. But do you know we can assign keyboard shortcut for the same or even we can customize the context menu in code editor to achieve the same as shown in below images.
How to use IIS Manager to get Worker Processes (w3wp.exe) details information ? November 4, 2010
Posted by Abhijit Jana in Debugging, General, IIS, Tips and Tricks, Visual Studio.Tags: ASP.Net, codeproject, Debugging, IIS 7.0, Internet Information Services, Tips and Tricks, WorkerProcess
6 comments
In one of my previous blog post, Identifying Worker Process (w3wp.exe) – IIS 6.0 and IIS 7.0 for Debugging ASP.NET Application - I have explained about how we can identify the list of currently running worker process using command prompt while we need to attach process from visual studio . But do you know for IIS 7.0 and IIS 7.5 we can get the worker process (w3wp.exe) details like Application Pool name, Process ID, CPU Usages from IIS Manager itself. Even you can get details of each worker process for a “Web Garden” scenarios. So when you need to attach some process for debugging from Visual studio, Instead of going to command prompt, you can easily identify the worker process Id from IIS itself.
Multipurpose Find Combo Box in Visual Studio November 1, 2010
Posted by Abhijit Jana in Tips and Tricks, Visual Studio.Tags: Beginners, codeproject, Find Combo Box, Tips and Tricks, Visual Studio
19 comments
Most of the time we use Visual Studio find combo box (
) only for search contents with in the solution. But the find combo box is something more than what we know. We can use the find combo box in different purpose like create file, open files, create project, print, open watch windows etc. As for example you can close all the open files by just typing “>CloseAll” with in find combo box followed by a “Enter”. Fundamentally we can execute all the commands from Find Combo box which are available from Visual Studio Command Window. Like Command Window, In Combo Box, if you type “>” and aliases and press enter result will be the same.
10 Tips you should know about “Watch Window” While debugging in Visual Studio October 26, 2010
Posted by Abhijit Jana in Debugging, Tips and Tricks, Visual Studio.Tags: codeproject, Debugging, Tips and Tricks, Visual Studio
18 comments
Watch windows is one of most commonly used debugging tool with Visual Studio. We generally used 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. But we can use watch windows for many different purposes. In this blog post I am going to show 10 Tips, that may help you while dealing with Watch Window.
How to track an object which is Out of Scope while Debugging ? October 20, 2010
Posted by Abhijit Jana in Debugging, Tips and Tricks, Visual Studio.Tags: C#, codeproject, Debugging, How To, Tips and Tricks, Visual Studio
20 comments
In Mastering in Visual Studio 2010 Debugging article I have discussed about the basic of Object ID creation while debugging. I received some request from some readers to explain the use of “Make Object ID” in details. In this blog post I am going explain how we can track an Object which is already out of scope using by creating a Object ID while debugging.
By using “Make Object ID” option we are informing Visual Studio Debugger to keep track of that object no matter it’s within scope or out of scope for the current context. We can create “Object ID” either from Locals, Autos or from Watch Windows. Object ID is a integer number followed by a pound (#) sign. When we create Object ID for an particular object, Visual Studio Debugger ( CLR Debugging Services ) use an integer value to uniquely identify the object. This “Object ID” allows you to get the object details even if it is out of scope.
Customize the Debugging Windows : Change Debugging Window View as per your requirements September 28, 2010
Posted by Abhijit Jana in General, Tips and Tricks, Visual Studio, Visual Studio 2010.Tags: codeproject, Customize Debugging Window, debuggertypeproxy, Debugging, How To, Tips and Tricks
3 comments
In this blog post I am going to explain how you can customize the complete view of the debugging window during debugging of application. By complete view means, where you can add own Properties, can customize the result, manipulate the data, hide properties which may not need during debugging etc. In one of my previous blog post, I have explained how we can customize the view of the debugging windows using DebuggerBrowseable and DebuggerDisplay attributes over Few Tips on Customizing Debugging Window View in Visual Studio . But, both these two attributes are limited to customize the view for a specific class and they can only show you the information for the particular class members . In this blog post you will see how we can create new view for some existing debugging view using “DebuggerTypeProxy” attributes. From the below snaps you can understand what kind of customization we can do inside a debugging window.
Tips on Debugging : Using DebuggerStepThrough attribute September 22, 2010
Posted by Abhijit Jana in General, Tips and Tricks, Visual Studio, Visual Studio 2010.Tags: Breakpoint, Call stack, codeproject, Debugging, Programming, Visual Studio
10 comments
In my few previous blog post I have explained how we can customize the Debugging windows view during debugging of application using “DebuggerBrowseable “ attributes and “DebuggerDisplay” , then I have also explained use of “DubuggerHidden” attribute which tells the Visual Studio debugger that the method is hidden from the debugging process and while debugging. In this blog post I am going to explain one similar features of “DebuggerHidden” attributes, named “DebuggerStepThrough”
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” attributes, that code block will be marked as “[External code]” in stack Trace. Where as “Debugger hidden” attributes didn’t marked is External code.
Color Indicator for Code Changes – Track Changes in Visual Studio 2010 September 14, 2010
Posted by Abhijit Jana in Tips and Tricks, Visual Studio, Visual Studio 2010.Tags: codeproject, Tips and Tricks, Visual Studio, Visual Studio 2010
15 comments
“Track Change” one of the best interesting features in visual studio which indicates the code changes with a color indicator at the beginning of the line. Generally we know about the two color indicator “Green” and “Yellow” which are used indicting the color change till VS 2008 along with those VS 2010 introduced another new color “Orange” which indicates some additional track change for undoing file after save. In this blog post I am going to explain how those color indicator helps developers to track the code changes.
In Visual Studio 2010, there is three color indicator
Green color indicates the lines which you have edited before your last save. Save again the file and green mark will be disappear.
Yellow color indicates the lines which you have edited since the last save of that file. Yellow becomes Green after saving of the file. Once you close the file that indication disappears.
This color indication has newly introduced in VS 2010. This color will come when user does an undo after a save operation for that current file. Orange color indicates that current changed line is different from the saved version of the file.
Use “Obsolete” attributes to indicate Obsolete Methods September 3, 2010
Posted by Abhijit Jana in ASP.NET, C#, General, Tips and Tricks, Visual Studio.Tags: Beginners, codeproject, How To, Obsolete, Tips and Tricks, Visual Studio
10 comments
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 this case if you changed the name or declaration of that method, application may crash in different point of times as it’s being used by other developer in the application. In this case you can use System.ObsoleteAttributes class to generate compiler warning and indicate the method as Obsolete.
