Is WF worth it? Convince me!

So, I came back from TechEd enthused and raring to go with the new Workflow technology. But, after installing the June CTP and working with it a bit I am becoming disillusioned.

The whole purpose of WF is to ease development and maintenance, is it not? It seems to be making my life harder - having to go into code and hardwire if-then CodeConditions and build events and interfaces out the wazoo to do some simple passing of data. Once these things are built, I have to try to explain it to other developers who may not be as up to date on WF concepts and it just seems like a mess.

Am I wrong? Will the benefits pay off in the end? Is the IDE interface just a bit immature and perhaps this is something that should be tabled and addressed again later?

[773 byte] By [KirkLipscomb] at [2007-12-22]
# 1
First time Adopters always have this problem. You face the issues of working with a very unpolished product. It costs you money and time and yet without people's real world usage and feedback to Microsoft the product will never improve. Nobody else can really tell you what choice is right for you, your situation, your employees and your company. You need to analyze it, and make that choice for yourself.
MarcD at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...

Software Development for Windows Vista

Site Classified