Search

Search:

Namespace:

Search Result
.

WindowsWorkflowFoundation uses the ActivitySurrogateSelector as the way to serialize and deserialize all Activities. Use the ChainSelector function to add any additional custom ISurrogateSelector required.

.

Some good resources if you are just getting started with WindowsWorkflowFoundation

.

The WindowsWorkflowFoundation team has released a large number of samples along with the first version of the product. You can download them from http://go.microsoft.com/fwlink/?LinkId=73348.

.

A Dutch Team System MVP who does a lot of WindowsWorkflowFoundation work. See his blog at http://blogs.infosupport.com/marcelv/default.aspx

.

See his article about WindowsWorkflowFoundation and the AmazonMechanicalTurk.

.

I did a few Dutch language ScreenCasts about WindowsWorkflowFoundation

.
Redirect
.

This page was automatically generated when this topic (Microsoft Products Building on Windows Workflow Foundation) was renamed to MicrosoftProductsBuildingOnWindowsWorkflowFoundation on 17-10-2006 at 9:38 by -127.0.0.1.

.

Download the MicrosoftOfficeSharePointServer 2007 SDK for WindowsWorkflowFoundation from http://www.microsoft.com/downloads/details.aspx?familyid=6D94E307-67D9-41AC-B2D6-0074D6286FA9&displaylang=en

.
       Image(federation.LinkMaker.LinkToImage("images/WindowsWorkflowFoundation3.png"), "command", "url")
.
  1. MicrosoftProductsBuildingOnWindowsWorkflowFoundation. They would not choose a toy technology. These products include Microsoft Office SharePoint Server 2007, Microsoft BizTalk Server "vnext", Microsoft Speech Server 2007, Microsoft System Center "Service Desk", Microsoft Identity Integration Server "future version", and Microsoft Dynamics "future version".
.

.

. .
.
Summary
A StateWorkflow is one of the two basic workflow models included with WindowsWorkflowFoundation.
.

A StateWorkflow is one of the two basic workflow models included with WindowsWorkflowFoundation, the other being a SequentialWorkflow. A StateWorkflow is basically an implementation of a FiniteStateMachine. The main advantage of a StateWorkflow is that the workflow can switch between states at will, either because of a SetStateActivity in an event handler or explicitly by using the SetStateQueue queue with a SetStateEventArgs argument indicating the target state.

.
Redirect
.

Download the MicrosoftWindowsSharePointServices 3.0 WindowsWorkflowFoundation SDK from http://www.microsoft.com/downloads/details.aspx?familyid=05e0dd12-8394-402b-8936-a07fe8afaffd&displaylang=en

.

WindowsWorkflowFoundation (WF) is one of the parts of the .NET 3.0 framework as released by Microsoft. One of the most interesting aspects of WindowsWorkflowFoundation (WF) is the separation between business process code and the actual implementation, often a requirement in ServiceOrientedArchitecture (SOA). Before WindowsWorkflowFoundation the typical scenario would be to write both the business logic and the actual implementation in CSharp (C#), VisualBasic .NET or another .NET language. The result was no clear separation between business logic and its implementation. With the release of Windows Workflow Foundation (WF) the business logic can be defined in the workflow while the actual underlying implementation is done in C#, Visual Basic .NET or another .NET language. So basically the what is done in the workflow and the how is done in traditional programming code.

.

WindowsWorkflowFoundation is basically a library consisting of an execution engine, a rules engine, a number of activities, a number of supporting runtime services and a designer allowing developers to design their workflows graphical in VisualStudio2005 (VS2005). In fact it even includes a graphical debugger allowing the developer to step through the workflow and even into the underlying .NET code. The engine is designed in such a way that the developer has a free choice between building the workflow as code constructs or in a declarative fashion using XAML. Either way he can use the graphical designer the same way, all that changes is the output. Because the runtime engine has the capability of parsing and executing the XAML itself we have tremendous flexibility in our workflows. There is no need to compile them at the same time as the rest of the application. This flexibility even goes further and the engine allows for the runtime alteration of the executing workflow, how about that for flexibility!

.

Because WindowsWorkflowFoundation is a library, not a standalone platform or service, the developer is completely free to include the WindowsWorkflowFoundation library in process in his own application or web site/service. This can be of great benefit to existing applications where using a separate workflow server, like BizTalk 2006, would be prohibitive. Because of the modular way WindowsWorkflowFoundation is designed, the developer is free to replace standard services like persistence, scheduling or tracking with another implementation if he or she so desires.

.

If you are new to WindowsWorkflowFoundation the GettingStarted page is a good place to do just that. Over there you will find some links to articles and videos about WindowsWorkflowFoundation that should give you a basic understanding. If you are already familiar with the basic of WindowsWorkflowFoundation you can use either the search box to the left to look for specific information or maybe start at the list of Activities. Another good starting point is WorkflowFoundationGotchas with a list of items that can cause problems if you are unaware of them.

.
Summary
.

The WindowsWorkflowFoundation team has released a large number of samples along with the first version of the product. You can download them from http://go.microsoft.com/fwlink/?LinkId=73348. Update, that link seems to be dead, use this http://msdn2.microsoft.com/en-us/library/ms741723.aspx one instead.

.
       Presentations.Image(federation.LinkMaker.LinkToImage("images/WindowsWorkflowFoundation3.png"), "WIndows Workflow Foundation", "http://www.WindowsWorkflowFoundation.eu")