UNIX Application Migration Guide (Patterns and Practices)

Features

• Cover Type: Paperback with 684 pages
• Published by: Microsoft Press April 23, 2003
• Written in: English
• ISBN 10 Number: 0735618380
• ISBN 13 Number: 978-0735618381
• Book Dimensions: 9 x 7.5 x 1.6 inches
• Weighs: 2.9 pounds

Reader Reviews
If you are an experienced UNIX developer looking for a book to help you port an application to Windows, then keep looking for another book. The only reason that I don't give this book a lower rating is that it actually does contain some useful information. In fact, it contains a great deal of useful information (along with a healthy dose of nonsense and fluff). However, you are unlikely to ever find the information you need as the book contains no index! How can anyone publish a technical book in this day and age without an index? UNIX Application Migration Guide is a hodge-podge of unrelated information. At times it degenerates into a step by step tutorial on using Visual Studio. I admit that this is useful information, but not at all related to the subject of the book. Some sections read as though the authors were relieved to find anything to fill the blank page as they sat at their word processors. The authors seem to believe that UNIX developers are unfamiliar with professional software development. One chapter is devoted to "Testing the Migration." The purpose of this chapter escapes me. While the stated goal is to provide a strategy for testing the migration, it offers little more than a reiteration of common software practices, with no practical advice on implementing them. For instance, are there any useful utilities under Windows for playing back a sequence of mouse and keyboard events to provide an automated GUI test environment? That would have been valuable information. Instead, the reader is treated to such silly advice as "The test team may resume testing if the problem that suspended the testing is corrected, or the development and test teams agree that fixing the bug can be postponed until the next iteration." Comments (2) | | (Report this)