Professional IronPython

2.
Click Step Over. You’ll move to the first line of the application. At this point, the debugger 
begins executing your application code.
3.
Click Step Over again. If you look at the command prompt at this point, you’ll see that it 
contains the expected output text, but not the answer, as shown in Figure 2-9. Now, if you 
clicked Step Over again, you’d see the output from the 
Mult()
function, but you wouldn’t 
actually see the code in 
Mult()
execute. The next step shows how to get inside a function so 
you can see how it works.
FIgURE 2-9: 
The console screen will show the results of tasks performed in your application code.
548592c02.indd 29
2/24/10 12:47:20 PM
www.finebook.ir

---

30
❘
CHAPTER 2
Understanding the ironPython Basics
4.
Press F5 or click Start Debugging. The application will stop within 
Mult()
. Being able to 
stop within a function is the reason for setting the second breakpoint at the beginning of this 
procedure. Now you can use Step Over to execute the lines of code one at a time. Notice the 
Debug History window. You can select entries in this window to see what the IronPython 
interpreter has been doing in the background, as shown in Figure 2-10.
FIgURE 2-10: 
Use the Debug History window to see what the interpreter is doing
in the background.
5.
Press F5 or click Start Debugging. The application will end.
Visual Studio does provide you with access to many standard debugging features. For example, 
you can place variables in the Watch windows and see their values as shown in Figure 2-11. You 
also have access to the Call Stack and Output windows. The Immediate and Command windows 
don’t work as you might expect them to, so you need to inspect variables and perform other 
variable-related tasks using the Watch windows.
FIgURE 2-11: 
The Watch windows provide access to variable information.
548592c02.indd 30
2/24/10 12:47:20 PM
www.finebook.ir

---