Support
Joined: 18 Jul 2005 Posts: 731
|
Posted: Wed Nov 25, 2009 5:05 am Post subject: INFO: Using debugging to track potential problems. |
|
|
Many times, certain functionality of your shell extension does not work due to coding issues. One way to determine the potential cause is to see if any exceptions are being raised/thrown. To do this, :
1. Under Project settings--> Debugging, specify Windows Explorer as the command (the typical path is "c:\windows\explorer.exe")
2. Under Debug Menu -->Exceptions, check 'Common Language Runtime Exceptions' and click OK.
3. Start the project under debug mode using F5. Windows Explorer will start running. If this does not work, start Windows Explorer externally (for example, by pressing the Windows+E key combination) and then attach to this Windows Explorer process (explorer.exe) using the 'Attach...' menu option from the 'Debug' menu in Visual Studio.
4. In Visual Studio, switch to the 'Output' tab where all diagnostic messages including exception information is displayed.
5. Browse the Windows Explorer and try to execute that functionality of the shell extension which is not working. If any exceptions are raised/thrown, information about the same will be shown in the 'Output' window. This information can be used to diagnose the possible cause of the problem, or the entire contents of the 'Output' window can be sent to technical support as a supporting document. |
|