1324 Visual Studio .NET Debugger Appendix (Web server application) D Control
1324 Visual Studio .NET Debugger Appendix D Control Button Shortcut Key Description Continue F5 Continues program execution. Execution continues until either a breakpoint is encountered or the program ends (through normal execution). Stop Debugging Shift + F5 Stops debugging and returns to Visual Studio design mode. Step Over F10 Advances to next statement, does not step into method calls. Step Into F11 Executes next statement. If the statement contains a method call, control transfers to the method for line-byline debugging. If the statement does not contain a method call, Step Into behaves like Step Over. Step Out Shift + F11 Finishes executing the current method and suspends program execution in the calling method. Fig. D.19 Fig. D.19Fig. D.FiFi19g. D.19g.D.19Debug program control features. Programmers can use the Immediate window, discussed in Section D.3 for testing method arguments passed to a method (Fig. D.20). Testing the arguments helps determine if a method is functioning properly. D.6 Additional Class Debugging Capabilities In most sophisticated C# programs, a large portion of program data is contained in objects. For these purposes, Visual Studio includes class debugging features, which allow programmers to determine the current state of objects used in a program. We demonstrate some class debugging features using the code presented in Fig. D.21. To examine an instance of class DebugEntry, we place a breakpoint at line 43, as shown in Fig. D.22. [Note: A C# file may contain multiple classes, as is the case with this example.] Fig. D.20 Fig. D.20Fig. D.FiFi20g. D.20g. D.20Using the Immediate window to debug methods.
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.