Not for nothing but Windows Workflow was always a go nowhere tech, to be honest. The best thing is to have a good foundation in fundamentals and don't get so bogged down in API. If a tech has an extremely complicated API and it is not doing something specialized like control a space shuttle then it might be best to look elsewhere. Anyway, I just feel like Windows Workflow was something only the most Microsoft infused government programming firm could love.
Workflow is one of those great examples of Microsoft building and ditching platforms/technologies. They've gone through almost as many cycles there as they have with data access technologies.
We have some cool stuff deployed with it (long term service correlation, long running background processes, custom workflows for business processes), but you are right about it being complicated. We're in the financial sector so workflow and process management is king to us.
The API is there for us to not have to do all the legwork. Do you know how complicated it is to produce a workflow engine and do you know how many companies have their own half broken workflow engines?
