Fixes a performance issue with the Serialization service when you use the System.Workflow.ComponentModel.WorkflowMarkupSerializer class for extensible Object Markup Language (XOML) in Windows Workflow Foundation

This article has been archived. It is offered "as is" and will no longer be updated.
You create a complex sequential workflow or a state-machine workflow by using Microsoft Visual Studio 2008. The workflow contains thousands of activities. When you use the System.Workflow.ComponentModel.WorkflowMarkupSerializer class to serialize the workflow into the extensible Object Markup Language (XOML) format, the serialization takes several minutes to be completed. During this period, the CPU usage for the devenv.exe process is high. However, deserialization of the workflow from the .xmol file takes only a few seconds.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


You must have the Microsoft .NET Framework 3.0 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you install the hotfix if no instance of Visual Studio 2008 is used.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
x86 and x64-based versions for Windows Server 2003 and Windows XP:

File nameFile versionFile sizeDateTimePlatform
Servicemodelreg.exe3.0.4506.73261,44007-May- 200922:39x86
System.workflow.activities.dll3.0.4203.10121,156,98424-Apr- 200914:52x86
System.workflow.componentmodel.dll 3.0.4203.10121,644,41624-Apr- 200914:52x86
System.workflow.runtime.dll3.0.420 3.1012599,92024-Apr-200914:52x86

To improve the efficiency of a workflow, divide the workflow into several smaller, simpler workflows.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For example, you serialize the workflow by using the following code snippet:
      Activty rootActivity;      StringBuilder xomlBuilder = new StringBuilder();    XmlTextWriter xmlWriter = new XmlTextWriter(new StringWriter(xomlBuilder));        //Add some activities into the rootActivity...    //then serialize the workflow as follows:     try    {       WorkflowMarkupSerializer xomlSerializer = new WorkflowMarkupSerializer();       xomlSerializer.Serialize(xmlWriter, rootActivity);    }

Article ID: 969544 - Last Review: 10/21/2013 20:50:47 - Revision: 1.0

Microsoft .NET Framework 3.0 Service Pack 1, Microsoft .NET Framework 3.5

  • kbnosurvey kbarchive kbexpertiseadvanced kbsurveynew kbqfe KB969544