Share via

Visual Studio 2005 Designer for Windows Workflow Foundation Overview

  • Article

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The Visual Studio 2005 Designer for Windows Workflow Foundation provides a means to rapidly develop workflows by using a graphical interface that leverages a developer's knowledge of the Microsoft Visual Studio development environment.

WF Workflow Markup

Each WF workflow can be represented by the following combinations of files:

  • An XML file, or markup,that includes the declarative metadata of the workflow; or

  • The markup file, in combination with a code-behind file that contains custom code representing the properties and behavior of the workflow; or

  • A code file (or files) that include both the declarative logic and behavior of the workflow.

The markup file is written in eXtensible Application Markup Language (XAML), which has a published schema to which the file must adhere, and given a file extension of .xoml.

Because the XAML has a published schema, you can create XAML files using any text or XML editor you choose. However, the Visual Studio 2005 Designer for Windows Workflow Foundation offers developers a graphical interface in which to create workflows, and automatically generate the appropriate markup file.

Developers can choose to integrate or separate their declarative metadata from the business logic included in the workflow. Conceptually, the "code separation" paradigm WF workflows employ is similar to that used in ASP.NET: declarative metadata is separate from the file that encapsulates your business logic. So, while the markup file contains the metadata for the activities included in the workflow, the properties and behaviors of those activities are detailed in a separate file.

For workflows authored using code separation, information is persisted in the two files:

  • The markup file, as detailed above.

And one of the following two types of files:

  • A code-beside file, which contains the code that encapsulates your business logic. This file may be written in either Microsoft Visual C# or Microsoft Visual Basic.

  • A workflow rules file, which encapsulates your business logic in declarative rules, rather than code.

Each workflow created this way is actually a unique Microsoft .NET type, constructed from two partial classes, which are represented by the XOML and a code-behind or rules file. When the workflow project is compiled, these two partial classes are combined into a .NET assembly. This is the approach taken when authoring workflows for Windows SharePoint Services 3.0 using the Visual Studio 2005 Designer for Windows Workflow Foundation.

Workflows comprised only of code files follow the same general compilation process: that is, the code files are compiled into a .NET type.

In addition, you can compile workflows comprised solely of markup files. However, this is not necessary; the WF runtime engine can load and run uncompiled markup workflows. This is the approach taken when authoring workflows for Windows SharePoint Services 3.0 using a declarative-rules-based, code-free workflow editor, such as Office SharePoint Designer 2007.

Visual Studio 2005 Designer for Windows Workflow Foundation Features

The Visual Studio 2005 Designer for Windows Workflow Foundation provides a means to rapidly develop workflows by using a graphical interface that leverages a developer's knowledge of the Visual Studio development environment.

The Visual Studio 2005 Designer for Windows Workflow Foundation is a tool for you to rapidly create the workflow in a way that is integrated with the development of the code encapsulating your business processes. To do this, the Visual Studio 2005 Designer for Windows Workflow Foundation provides a graphical interface with intuitive controls, hosted within the familiar Visual Studio development environment. Its features include the following:

  • A drag-and-drop design surface that lets you assemble custom workflows from predefined workflow activities you drag from the Toolbox.

  • An interface that lets you work on your workflow markup using intuitive graphical tools.

  • Integration with the Properties window, so developers can configure properties of workflow activities either through the graphical interface or directly in the code-beside file, and always keeps the two in sync.

  • Debugging of your workflows by attaching to the SharePoint process, including setting breakpoints in your workflow.

  • The ability to attach error, compensation, and event handlers to activities, and ‘comment out’ activities graphically.

The Visual Studio 2005 Designer for Windows Workflow Foundation is available as part of the download titled Visual Studio 2005 Extensions for Windows Workflow Foundation available on the Microsoft Download Center. This download also contains the Windows Workflow Foundation runtime engine, as well as the Windows Workflow Foundation SDK.

For more information about the Windows Workflow Foundation, including using the Visual Studio 2005 Designer for Windows Workflow Foundation to create workflow solutions, refer to the Windows Workflow Foundation SDK or visit the Windows Workflow Foundation Developer Center.

For more information about configuring a workflow project to develop a Windows SharePoint Services 3.0 specific workflow template, see How to: Manually Configure a Workflow Project.

See Also

Concepts

Workflow Development for Windows SharePoint Services

Workflow Activities for Windows SharePoint Services Overview