Customer comments on this selection.
 Nothing short of a Masterpiece
I have been pretty heavy into WF for almost 2 years now and really thought I had it mastered. So when I bought a Step by Step book, I really just wanted it to help me teach the concepts. B/c workflow is a new way of thinking about programming, I'm always looking for new/better ways to teach it.
br /
br /What I got instead of a beginner's book teaching worfklow foundation was a big slice of humble pie. Why do I say that? B/c this book is nothing short of amazing. It's unbelievably well written. There is no stone unturned, and I mean no stone unturned whatsoever. The examples are compelling and are very real world. In fact, they show beyond any shadow of a doubt that Workflow foundation can be used all over the place - essentially anywhere you need a workflow. While that last statement may seem strange, it really isn't. THe hardest thing I've seen most people wrestle with learning WF is realizing that's it's not just applicable in some external rare/specific circumstances. You can (and should) use it anywhere you have a series of steps that must be executed together.
br /
br /One critic knocked the book b/c the author takes off on so many digressions code wise. How anyone could level this charge against the author is beyond me - in fact, it's borderline heresy. The digressions (if you want to call them that - I think they're better described as "Real World" uses) are what makes this book shine.
br /
br /One application shows a mock stock trading system that runs Monte-Carlo simulations on the stocks. It allows you to add/remove stocks and run the simulations repeatedly. This is something that most folks would never think to do with WF, yet his presentation of it is so elegant and intuitive that I challenge anyone who's honestly worked through his examples to say that it didn't change the way they thought of WF afterward.
br /
br /In another case, to show State Machines, he walks through a sample Soda Machine. Not only is it a clever way of implementing a State Machine, it is as perfect of an example as I think you could come up with.
br /
br /Although I'm hard pressed to say I had a favorite chapter, I'd have to cite Chapter 13 as a favorite just b/c, well, it really explains in depth how Microsoft uses Workflow Actvities all over the place in products like Microsoft Speech Server, SSIS or Biztalk. He doesn't talk about those per se, but if you've used them, you no doubt are familiar with the workflow designers. Each of them has its own set of custom activities. He walks throug buidling a FTP component that is reminiscent of the one that SSIS uses. If he just stopped at building the activity itself, no one could say he skimped on the lesson. But he continues, walking you through building a ActivityValidator and then building full UI support for it as a Toolbox item. When you're done, you'll see something that looks and feels almost identical to the FTP component in SSIS from start to finish. No detail is left uncovered. And at that point, every activity you've used in any one of those products will look different to you - in the sense that you'll probably be able to reverse engineer them in your head. If not, I think you'd definitely be able to build one of your own for any given activity you've used in those products.
br /
br /It's really hard to fathom how much thought the author put into coming up with the examples. But he was dead set on making sure that you understood exactly what you can do with workflow and how many different scenarios it is applicable to. Throw in some really in-depth coverage, a really compelling writing style and an uncanny ability to cover the tiniest of nuances all the while being appropriate to both beginners and experts and you have exactly what I described at the onset - a Masterpiece.
br /
br /I really don't think there's a single thing in this book I could take issue with or say could be done better. And that's coming from someone who teaches WF and pretty much has lived and breathed it since it's earliest bits were released. I wanted something to help me teach WF and I got way more than I bargained for.
 What's so "step by step" about it?
You know it's not good when you're reading a technical book like this and the whole time you're scratching your head, asking yourself, "What's going on here?" I'm not referring to the sentence-by-paragraph writing style. I'm talking about the overall organization of the book. It's called "step-by-step", but it really isn't unless you are a 2-year-old who can't yet count straight from 1 to 10.
br /
br /For instance, it seems reasonable, especially in a self-proclaimed "step-by-step" book, that a chapter called "Basic Activity Operations" would be Chapter 1 or 2, maybe 3 if there's a lot of intro material. But no. In this book, that chapter is Chapter 7. Meanwhile, the first 6 chapters deal with all kinds of things from writing code that you don't actually need "in real life" to things I would consider advanced topics (or at least intermediate), like persisting Workflow processes on a hard drive in case of loss of power to the machine doing the processing. And here I am, especially on the persistence chapter, thinking, "Why on this green earth do I need to know about persistence yet, when I don't even know about 'basic activity operations' yet???"
br /
br /The author also has a habit of going off on tangents for a couple of paragraphs and then cutting himself off with, "But enough of that. We'll get to it again in a later chapter." Or, in reverse, sometimes he leads into a tangent with, "We're not going to discuss this in detail for another 10 chapters, but here's what I want to say about it now..." Dude! STAY ON THE TOPIC AT HAND!!!
br /
br /The irony is that I just advised someone else to stay away from books published by Microsoft Press. But this was an emergency purchase made at a local bookstore (sorry Amazon), and this was the only book available on the topic of Workflow on the store's shelves. Suffice it to say, I've had to relearn the lesson that Microsoft Press publishes CRAP, because they're too close to their own products.
br /
br /I DO NOT RECOMMEND THIS BOOK. Go with something published by Apress or anyone else, but not Microsoft Press!
just not for me
If you need a 'hit the ground running' type of book, this is not for you. Also this book is not for C# rookies, the first samples have topics such as generics and threading.
br /
br /I'm a 'learn by doing' kinda guy, and before writing any code sample, it helps me a LOT to know if I will be using this in the real world and most importantly, under what scenario. Knowing this gets my mind racing and motivates me to continue reading.
br /From what Ive seen, these Microsoft Step by Step guides have a different approach where they begin by teaching how to do things giving 'technical whys', and not 'business solution whys'. From this standpoint I prefer the Pro Apress books.
br /
br /
 Excellent intro to Microsoft Workflow Foundation
My original goal was coming up to speed on SharePoint development. I am writing a connector between SharePoint and a third-party database. The workflow chapter in the SharePoint book by Pattison was very useful but didn't provide enough detail. Scribner's book provides a wonderful introduction to workflow and takes up where the Pattison book left off. The book has an informal style and lots of examples, and is a quick read, but along the way it describes what is going on in a way I find very satisfying. The Table of Contents is very helpful in planning my approach to reading the book. There is no explicit mention of SharePoint in the book, but it is pretty clear which chapters are relevant to SharePoint development.
 Make the hand-on labs on MSDN, is the same
This book was not precissely what I expected.
br /If you already know something about WF but you want to go deeper in the technology this is NOT the book for you.
br /The book is pretty basic and doesn't explain in detail all the aspects about the technology.
br /If you are looking for just to put a sales order process up and running in 1 day without much complication, then this is the right book for you.
br /The only reason I bought this book was O'Really doesn't have yet a publication about this topic.
br /Then, buy it if you know NOTHING, ZERO, about WWF. Otherwise you'll get bored and hungry about more technical details like me.
|
