1. ASP.NET Introduction 2. Comp of .Net Framework 3.5 3. Sys.Req for VS 2008 4. ASP.NET Envrmnt Setup 5. VS2010 Ultimate Sys.Req 6. Installing VS 2010 7. VS 2012 Sys.Req 8. Installing VS Exp 2012 9. Start the VS 2008 10. Application Life Cycle 11. Page Life Cycle 12. Page Life Cycle Events 13. ASP.NET Example 14. Event Handling 15. Default Events 16. Server Side 17. Request Object 18. Response Object 19. Server Controls 20. Server Controls Properties 21. Server Controls Methods 22. HTML Server Controls 23. Client Side 24. ASP.NET Basic Controls 25. TextBox Control 26. CheckBox Controls 27. RadioButton Controls 28. ListBox Control 29. HyperLink Control 30. Image Control 31. BulletedList Control 32. ASP.NET Directives 33. Implements Directive 34. Master Type Directive 35. Page Directive 36. PreviousPage Type 37. Managing State 38. Control State 39. Cookies 40. Query Strings 41. Server-Side State 42. Session State 43. Validation Controls 44. Required FieldValidator 45. Range Validator 46. Compare Validator 47. RegularExpressionValidator 48. Custom Validator 49. Validation Summary 50. Data Source Control 51. AdRotator Control 52. Calendar Control 53. Calendar Control Example 54. Panel Control 55. Panel Control Example 56. Multi Views Control 57. MultiView & View controls 58. MultiView Control Example 59. FileUpload Control 60. FileUpload Control Eg 61. AJAX Control 62. UpdatePanel control 63. UpdateProgress Control 64. Custom Controls 65. Custom Control Eg 66. Personalization 67. Create Simple Profile 68. ADO.NET 69. ADO.NET Objects 70. DataTable 71. DataRow 72. DataColumn 73. Object Example 74. Error Handling 75. Tracing Errors 76. Debugger 77. Security 78. Authentication 79. Authorization 80. LINQ 81. LINQ Query Operators 82. LINQ Example 83. Caching 84. Data Caching 85. Output Caching 86. Object Caching 87. Web Services 88. Create Web Services Eg 89. Web & Machine.config 90. Settings Schema 91. ASP.NET Deployment 92. XCopy Deployment 93. Web Setup Project 94. ASP Interview Part 1 95. ASP Interview Part 2 96. ASP Interview Part 3 97. ASP Interview Part 4 98. ASP Interview Part 5 99. ASP Interview Part 6
Pr.Pg Next Pg

ASP.NET- Debugger tutorials

  • Visual Studio has always provided the developer with very powerful GUI debuggers, and Visual Studio .NET is no exception to this tradition.

  • The debugger built into Visual Studio .NET is powerful and has a lot of new features compared to the debugger that was available with Visual Studio 6.0. Features that were previously available to the developers of Visual Basic only, like the immediate window, are now common to all the .NET languages. So, irrespective of the language that is used to create a Web application, the debugging tools remain the same, thereby delivering a better developer experience.

  • You can use the Visual Studio .NET debugger to debug applications in one of the following two ways:

    1. By using the Debug menu

    2. By manually attaching the debugger to a running application

  • The debugger provides many options that allow you to check for any errors by running through the code step by step, skipping a code routine, or placing a breakpoint. A breakpoint marks a point in the code at which the application halts and enters a mode called Break mode. The different options available in this mode help a developer to trace the source of an error in an application.

Using the Debug menu

  • To debug an application, select Debug ->Start. This option starts the application and attaches a debugger to it.

  • The different Debug menu options are described in the below table.





Used to start the application execution


Used to continue the application execution after the application enters a break mode.


Used to restart the debugging process

Step Into

Used to transfer the control to a called procedure in the application

Step Out

Used to transfer control from the called procedure (without proceeding further) back to the calling procedure.

Step Over

Used to skip a called procedure

Run To Cursor

Used to execute the code until it reaches the line where the cursor is placed, or until a breakpoint is reached, whichever occurs first.

New Breakpoint

Used to set a breakpoint on any line of code.Using the New Breakpoint dialog box (Ctrl+B) provides a lot of options such as to specify additional conditions that must be met for a breakpoint to be hit, and when the breakpoint will be hit .An alternative to set a breakpoint is to click the left margin of the line where you want to set a breakpoint.


Note: The Step Into and Step Over options perform the same operation until the code reaches a calling statement to call a procedure. The Step Into option causes you to enter the called procedure and run through it, whereas the Step Over option causes you to skip any called procedure.


Attaching a Debugger:

  • In addition to attaching a debugger to an application when you start it, you can attach a debugger while an application is already running.

  • To do so, complete the following steps:

    1. Open the application in Visual Studio .NET.

    2. Select Debug Click on Attach to Process..

    3. Ensure that the "Default" option is selected.

    4. In the Available Processes pane, all the processes are listed. Scroll through the list to select aspnet_wp.exe.

    5. Click Attach to open the Attach to Process dialog box. From the available choices, select Common Language Runtime and Script.

    6. Click OK and then click Close.

  • After you've attached the debugger to your running application, you can debug the application to trace the source of error.

Note You can attach a debugger to a running Web page only if it is running in Internet Explorer. If you are viewing the page within the IDE, you will not be able to attach a debugger with your page.


Pr.Pg border                                              Next Pg