Professional IronPython

Accessing the dialog Box Library from IronPython
At this point, you have a nice collection of dialog box and form classes to use in an IronPython 
application. Of course, a production application would probably have quite a few more forms in 
it, but you have enough for testing and experimentation purposes. The following sections describe 
how to use these classes.
An Alternative Method for Adding the IronPython Project
There are a number of ways to configure a test setup for your extensions. The section “Adding the 
IronPython Project” earlier in this chapter shows one technique. The technique works well when 
you want to maintain separate builds of your extension. However, you might want to maintain 
just one build — the build you’re currently using for debugging, testing, or experimentation. Use 
the following steps to create a centralized test configuration.
1.
Right-click Dialogs in Solution Explorer and choose Properties from the context menu. Select 
the Build tab. You see the Properties window shown in Figure 16-12.
2.
Click Browse next to the Output Path field to display the Select Output Path dialog box 
shown in Figure 16-13. Because you’ll add the IronPython test file at the solution level, you 
need to send the output to the solution level as well.
fIgURE 16-11: 
The Windows Form 
can contain any level of complexity 
you desire.
548592c16.indd 343
2/24/10 12:49:25 PM
www.finebook.ir

---

344
❘
CHAPTER 16
ExtEnding ironPython Using C#
fIgURE 16-12: 
Configure the build to use a central output location.
3.
Select the first Dialogs entry in the list and click OK. 
Visual Studio adds an absolute path to the Output 
Path field that you must change for every machine 
that uses the application. As an alternative, you 
could type ..\(two periods and a backslash) in the 
field to place the output in the solution folder.