Building Solutions with the Microsoft .NET Compact Framework: Architecture and Best Practices for Mobile Development

Although the title tells us this is a .NETcf book, you should pay attention to the subtitle, as the topics of architecture and general advice on mobile development are also covered at considerable length. This may or may not please you, depending on your role. For example, the chapter on security includes general theoretical principles on the topic but omits examples of using the Cryptography API. We notice this in other parts of the book, and in fact the first chapter is a pure retrospection into the history of mobile devices as supported by Microsoft. Add to my previous comments that the book is only 350 pages long and the fact that there are no complete/end-to-end code examples, and you can see why it is not aimed at programmers. To be fair, the authors don't hide this and they state in their preface that the target audiences are technical managers and architects.

Like anything that goes to print, there are some errors including: the recommendation of using ResEditor (it simply does not work with the CF); the suggestion that C# is 100% compatible between desktop and compact frameworks (what about `volatile'?); and the claim that the class loader ignores the build & revision number (or that for private assemblies the version number is not consulted), which is not true. Overall, though, the content is correct and for technical managers this is probably the best book on the subject (but certainly not for developers). Finally, a small note that there is no mention of SmartPhone 2003 since the writing must have been completed prior to its launch (or indeed prior to CE 4.2).

Why would you want this book? Well, most importantly it really explains the Why's of Compact Framework development. There really are a lot of considerations and while the CF is very similar to the full framework, there are a lot of differences. As a developer, this book thoroughly explains what you are getting into and how to avoid many common mistakes. However, even if you are a non-technical person this book will prove to be a great asset if you are involved in decision making. After all, who wouldn't want a mobile presence for their company? Well, like everything else, it comes with some strings attached. In most instances they are trivial compared to what you get. In others they may not be. Architectural considerations are critical because you are dealing with limited battery life, smaller processors and memory and reduced real estate. It's also a lot easier to lose a PDA than it is a desktop and since many of the advantages of using Handhelds are only realized when you have wireless access, issues like bandwidth and security can make or break any mobile initiative.

I think the best part of this book is its theoretical focus. It's very easy to run off and start coding, forgetting architectural concerns. In these instances, many find that getting a great little app that works great in a test environment isn't so good once you get it into production. This book can help you minimize the chances of that happening. Furthermore, it gives you a very sober perspective on what you will need to deal with. Due to the fact that the CF has only been commercially released for under a year, and PDA development hasn't been a practical reality for more that a few years, there just isnt' that much literature out there. And this book's focus on architectural issues and HOW TO Deal with them effectively will prove how hip the authors really are.

I've been really impressed with the recent direction of AW and they've been pumping out some really great titles. Couple a good publisher with some really informed and talented writers and you have a winner. Undoubtedly, this book is a winner.