Function of the WorkflowCompiler type used to compile both XOML and code workflows.

One reason to use tis might be with generic parameters, something not supposted in XOML workflows. Use a custom serializer to enable this.

Dim reader As XmlReader = XmlReader.Create("workflow.xoml")

Or in case you prefer the XOML like this:

Nice sample application showing how to edit XOML using a rehosted designer.

Sometimes you just want to be able to create a workflow in code bus save it as a XOML workflow so the end user has the opportunity to modify it.

using (XmlWriter writer = XmlWriter.Create("MyWorkflow.xoml"))

This produces the following XOML workflow:

The WorkflowServiceHost loads the workflow definition at the moment it starts listening for incoming requests. This workflow defintion is cached so if you are using XOML based workflows and change the XOML you will need to restart the hosting service to activate the new XOML. The reason for this is that the WCF interface defintion can be part of the workflow itself so changing the workflow could actually mean changing the public interface the WorkflowServiceHost is exposing.

Dim reader As XmlReader = XmlReader.Create("workflow.xoml")

ErrorsLoadingXoml

CompileProblemsUsingXoml

Looking for a workflow XOML editor sample? Take a look at WFPad.

The XML language used for workflows is actually the XAML language. Because applications bind to specific file extensions and there is a distinct difference in what you can do with WorkflowFoundation XAML versus PresentationFoundation XAML the decision was made to use XOML as the file extension for XML based workflows.

XomlAndDeclarativeRules

in the RuleConditionEditor and everything works just fine. When you create a XOML based workflow this does not work. The activities added have a private scope and are not visible by the rules engine. The expression above, even though the RuleConditionEditor claims it is perfectly valid, will produce an error with the following text:

If the WorkflowCompiler is used, ie XOML with code beside, this is a compile time error. If the workflow is loaded as pure XOML this is a runtime error.

works exually well in both code and XOML.