Seeing a book like IronPython in Action, by Michael Foord and Christian Muirhead, is another milestone for IronPython. This is a solid work in every aspect, and something nobody using IronPython on .NET should be without. The book is chock full of useful information, presented along with a series of running examples, and covers almost every aspect of IronPython use imaginable.There are some introductory chapters -- some fluff about .NET and the CLR, an introduction to Python, and an introduction to with .NET objects from IronPython. The Python introduction has a slight emphasis on differences between IronPython and CPython, though there aren't enough to fill a chapter. This is a good thing! The chapter does a pretty good job of teaching Python, assuming you already know programming. In general, the book is aimed solidly at professional software developers: unless you are paid to do it, why would anyone want to get intimate with Windows?
During his review of ‘IronPython in Action’ Guido describes programming WinForms as ‘still looks incredibly tedious to create the simplest of UI’. This is a little unfair. Let me make my case. Firstly MS are not looking to make IronPython a major desktop application language – it could have been but is not in VS2010 with a GUI editor. For now the focus is elsewhere. So if you work with desktop applications and IronPython things are a bit ‘by hand’. Having been hacking various desktop tools, experiments and oddities for several years, I feel qualified by experience to say it is a pretty good state compared with wxPython, Tkinter and some of the web frameworks.Note that IronPython in Action does demonstrate how to use the Visual Studio winforms designer with IronPython, and discusses when it is better to use a designer and when to handroll code.