Professional IronPython

xx
IntroductIon
downloading and installing your copy of IronPython. You must also have a text editor — even 
Notepad will do, but it won’t be very convenient to use.
If you want to get full use out of this book, however, you must have a copy of Visual Studio.NET 
2008 or above. The book examples rely on Visual Studio.NET 2010. You won’t be able to work 
with the examples later in the book unless you have a copy of Visual Studio. In addition, a number 
of the techniques, such as debugging, require that you have a copy of Visual Studio.NET. Nothing 
has been tested with the Visual Studio Express Edition products, and there’s no guarantee that any-
thing will work with this edition of the product.
conventIons
To help you get the most from the text and keep track of what’s happening, we’ve used some
conventions throughout the book. Typical examples follow:
Notes, tips, hints, tricks, and asides to the current discussion are offset and 
placed in italics like this.
A warning tells you that something terrible will happen should a particular event 
occur. For example, if you perform a task incorrectly, you might see data loss.
As for styles in the text:
➤➤
We highlight new terms and important words when we introduce them.
We show keyboard strokes like this: Ctrl+A.
➤
➤
➤
➤
We show filenames, URLs, and code within the text like so: 
persistence.properties
. 
➤
➤
We show text you should type directly like this: type Hello for regular text and type
MyFile.py
for code and filenames.
➤
➤
We show text that you should replace with your own values like this: 
MyName for regular 
text and 
MyVariable
for code and filenames.
We present code in the following way:
➤
➤
We use a monofont type with no highlighting for most code examples.
548592flast.indd 20
2/25/10 12:10:15 PM
www.finebook.ir

---