Workflow still matters


As we said yesterday, workflow still matters, and I'm catching this stuff again in the Realworld(tm), trying to clear concepts and how-tos in these (not so) new componentes of .NET. Workflow Foundation is one of these, and I'll try to talk also about WCF, WPF/Silverlight, etc. from here and beyond.

So I'll start with one simple but interesting question. Let's assume you need to develop some business logic in .NET...

...is there any reason for not using Workflow Foundation?

Note that I'm not asking about doing all-or-nothing using WF. It's just a matter of searching for a reason for not using it as a part of the solution.

I'll try to look for the anwser for myself but, anyways, comments/discussions are welcome!


Comments (4)

  1. Andy Mackie says:

    I think there are two different questions:

    (i) Is there any reason for not using Workflow ?

    (ii)Is there any reason for not using Workflow Foundation ?

    The reason we haven’t used Workflow Foundation is that it doesn’t provide an out-of-the-box workflow server, for human-based workflow scenarios. Sure, WF provides the building blocks for creating a workflow server, but why go to all that trouble when you can buy workflow servers off the shelf, which have been proven in the field over many years.

  2. dario-g says:

    In short: Workflow Foundation is not end-user friendly 🙁

  3. I do believe WF can be used in many scenarios. I thought about it before and all project I’ve participated in, using .NET, would have a better solution using Workflow Foundation. And sometimes you just don’t have to develop your workflow server, but use Sharepoint Workflow, for instance if you wanna build a workflow to control tasks execution.

Skip to main content