Developing a Basic Net Xml Application

A .NET XML application will follow most of the same principles you use when working with a static language such as C or Visual Basic.NET. In fact, you might not notice much difference at all except for the obvious structural requirements of a Python application. Consequently, you should find it easy to move your XML code over to IronPython because you really don't have anything new to worry about. Listing 13-1 shows a simple XML application that creates an XML document, saves it to disk, reads...

Using The Ironpython Console

The IronPython console is the best place to begin working with IronPython. You can enter a few statements, test them out, and then work out additional details without too many consequences. In addition, because the console is interactive, you obtain immediate feedback, so you don't have to wait for a compile cycle to discover that something you're doing is completely wrong. In fact, even after you've mastered IronPython, you'll find that you use the console to try things out. Because IronPython...

Working with String objects

Strings are one of the first objects many people use. You write that first Hello World application and marvel when the words appear on screen. In fact, strings are the mainstay of many applications. Without strings you can't provide prompts to the user or ask for input. Sure, you may not do any heavy lifting with strings, but every application out there requires strings to work properly. The following sections discuss the IronPython string object in more detail. One of the problems you can...

Understanding Early and Late Binding

When you work with a class, you create an instance of the class, set the resulting object's properties, and then use methods to perform a particular task. COM lets you perform essentially the same set of steps in a process called early binding. When you work with early binding, you define how to access the COM object during design time. In order to do this, you instantiate an object based on the COM class. These sections provide an extremely simplified view of COM. You can easily become mired...

Debugging With The Clr Debugger

The CLR debugger, CLRDbg.EXE, is part of the .NET Framework SDK. You find it in the GuiDebug folder of your .NET Framework installation or in the Program Files Microsoft.NET SDK v2.0 GuiDebug folder. However, if you installed Visual Studio without installing the SDK, you might not see a GuiDebug folder. In this case, you can download and install the .NET Framework SDK separately. You can obtain the .NET Framework SDK for various platforms at these locations. .NET Framework 2.0 .NET Framework...