Windows Workflow Foundation (WF) is Microsoft’s activity-based framework for modeling and running workflows inside applications. A workflow is one activity or a tree of activities; a host process runs it through the WF runtime, which can coordinate execution and services such as persistence, tracking, and fault handling. WF is not supported in .NET 6 or later; Microsoft points to CoreWF as an alternative for modern .NET.
What is a workflow in WF?
Microsoft defines a workflow as a model of a real-world process made from elemental units called activities. The model describes the execution order and dependencies between pieces of work, which may be short-running or long-running and may be performed by people or by system functions. In WF’s terminology, an activity is a unit of program behavior, while a workflow can be a single activity or a tree of activities invoked by a host process.
As an Amazon Associate I earn from qualifying purchases.
This activity model lets an application represent a process as a composed definition rather than as one undifferentiated block of code. Activities can be composed declaratively, or their behavior can be authored in managed code. See Microsoft’s Windows Workflow Overview and WF glossary.
Recommended Free Tools
How does Windows Workflow Foundation run a workflow?
A host application uses the in-process WF runtime to execute workflow instances. The runtime provides the environment in which activities run and coordinates capabilities useful for long-running application processes, including flow control, exception handling and fault propagation, persistence of workflow state, loading and unloading in-progress instances, tracking, and transaction flow.
#1 Best Overall
The host’s interaction model depends on how the application needs to run the workflow:
- WorkflowInvoker: invokes a workflow in a manner similar to calling a method.
- WorkflowApplication: gives the host explicit control over one workflow instance.
- WorkflowServiceHost: supports message-based interactions across multiple workflow instances.
These are different hosting approaches, not different definitions of a workflow. Microsoft’s Windows Workflow Architecture describes the runtime and activity model, including how custom activities can schedule child activities, create bookmarks, perform asynchronous work, and register transactions.
Rank #2
What is WF used for?
WF is intended for applications that need to represent coordinated work as an executable process, particularly when that work involves dependencies, interactions, or long-running execution. For example, an application can model a sequence of system operations and human tasks as activities, then let its host run and manage an instance through the WF runtime. The framework supplies workflow-oriented execution facilities; the application still defines the process and its activities.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Is Windows Workflow Foundation supported in modern .NET?
No. Microsoft’s porting guidance says Windows Workflow Foundation is not supported in .NET 6 and later. WF documentation and examples should therefore be treated as .NET Framework-specific unless a project or library explicitly provides another implementation. Microsoft’s guidance points to CoreWF as an alternative; this does not by itself establish that every existing WF definition, custom activity, or application can be migrated unchanged. For a migration, verify the chosen implementation’s current documentation and compatibility with the workflow features the application actually uses.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
