Windows Workflow Foundation

From Wikipedia, the free encyclopedia

Jump to: navigation, search
This subsystem is a part of .NET Framework 3.0

Windows Workflow Foundation (WF) is a Microsoft technology for defining, executing, and managing workflows. This technology was first released in November 2006 as a part of .NET Framework 3.0.

Workflows, like traditional programs, allow you to coordinate work but have some important differences.

  • Workflows can handle long running work by persisting to a durable store, such as a database, when idle and loading again once there is work to do
  • An instance of a workflow can be modified dynamically while running in the event that new conditions require the workflow to behave differently from the way it did when it was created
  • Workflows are a declarative way of writing programs by linking together pre-defined activities rather than an imperative programming model of writing lines of code
  • Workflows allow you to declare business rules that are separated from your code making it easier for you to modify them in the future
  • Workflows support different styles of systems with sequential and state machine workflows

Microsoft has indicated that workflows are going to be a cornerstone of the future Service Oriented Architecture platform announced in October 2007 codename Oslo

Contents

[edit] Authoring Workflows

XAML is commonly used for declaring the structure of a workflow. However, the workflow may also be expressed in code using any .NET-targeted language (VB.NET, C#, C++/CLI, etc.).

WF provides .NET developers with the ability to separate the logic of their application from the underlying execution components, thus providing a clearer, more manageable representation of the application. This approach lends credence to the growing process-driven application methodology which aims to separate an application's logical flow from its executable components at an enterprise level.

Workflows comprise 'activities'. Developers can write their own domain-specific activities and then use them in workflows. WF also provides a set of general-purpose 'activities' that cover several control flow constructs.

Windows Workflow Foundation is supported by a companion set of extensions to Visual Studio 2005. These extensions contain a visual workflow designer which allows users to design workflows, a visual debugger which enables the users to debug the workflow designed, and a project system which enables the user to compile their workflows inside Visual Studio 2005. In Visual Studio 2008 WF functionality is included.

[edit] Moving data through Workflows

Activities that require or provide data can use properties to expose them, and enable the Workflow author to bind them to the containing workflow by declaring 'dependencies'.

[edit] Hosting Workflows

The .NET Framework 3.0 "workflow runtime" provides common facilities for running and managing the workflows and can be hosted in any CLR application domain, be it a Windows Service, a Console, GUI or Web Application.


The host can provide services like serialization for the runtime to use when needed. It can also hook up to workflow instance's events such as their becoming idle or stopping.

[edit] Communicating with Workflows

WF provides several ways to communicate with a running instance of a Workflow:

  • A Windows Communication Foundation approach to workflow communication was added in .NET Framework 3.5. Workflows which include a ReceiveActivity expose a selected interface method as a WCF service. This could allow external code to, for example, make a Web Services call to a running workflow instance. WF provides infrastructure to ensure that if a WCF call is made to a workflow instance that is idle (i.e. waiting for some external event like a WCF call or a timer event), then the instance will be loaded from storage into memory so that the message can be delivered. Workflows which include a SendActivity are, in turn, able to call external services via WCF.
  • When a workflow instance is created, the host application can provide information in Dictionary objects. Similarly, the Workflow can pass the results of the workflow to the Host application through a Dictionary Object.
  • The Workflow foundation also allows the Workflow to update the Host application of the progress of the workflow. This is done by raising events in the Workflow to which the host application will subscribe.

[edit] Types of Workflows

Using the WF foundation, three different types of Workflow can be created:

  • Sequential Workflow (Typically Flow Chart based, progresses from one stage to next and does not step back)
  • State Machine Workflow (Progress from 'State' to 'State', these workflows are more complex and return to a previous point if required)
  • Rules-driven Workflow (Implemented based on Sequential/StateMachine workflow. The rules dictate the progress of the workflow)

[edit] Products Using Workflow Foundation

[edit] WF Related project types in Visual Studio 2008

  • empty workflow project
  • sequential workflow library
  • sharepoint 2007 state machine workflow
  • state machine workflow library
  • sequential workflow console application
  • sharepoint 2007 sequential workflow
  • state machine workflow console application
  • workflow activity library

[edit] Books

[edit] Localised links

Personal tools