Compared To Windows Workflow Foundation

Objectflow as compared to MS Workflow Foundation

WF (Workflow Foundation) makes it easy for anyone to modify workflows through a designer, even business analysts and managers. While this is convenient for business people, it makes it very difficult for a developer to do their job well. After all, how is a developer supposed to effectively use tools like source control when core logic (workflow) is stored in a database and is in a constant state of flux. How can you even effectively write unit and integration tests in a system like this? For these reasons, it is nearly impossible to maintain quality in a system built around WF unless you ignore it's strongest features.

WF and Objectflow solve different problems. The goal of Objectflow is to throw together workflows with minimal amounts of code. Objectflow makes it easy to quickly put up a lot of infrastructure around your workflow, like an integrated security model, UI integration for presenting all possible choices to a user, and error handling. Objectflow is also built to work beautifully with concepts such as dependency injection and plain ol' object oriented design.