Select the product you need help with
Workflows gradually take longer to load in a workflow designer that is re-hosted in the .NET Framework 2.0Article ID: 981145 - View products that this article applies to. On This PageSYMPTOMSConsider the following scenario in the Microsoft .NET Framework 2.0:
CAUSEThis issue occurs because the number of items in an internal WeakHashtable structure increases. Each child activity in the custom container activities has read-only properties in the workflow designer. In this situation, items that correspond to the read-only properties are added to the WeakHashtable structure. However, these items are not removed after garbage collection. Therefore, the size of the structure gradually increases. When you load a workflow, the workflow designer accesses these items several times. Therefore, an increase in the structure size leads to an increase in the time that a workflow takes to load. RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have the .NET Framework 2.0 Service Pack 2 (SP2) or the .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply the hotfix if affected files are not being used.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.For all supported x86-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XPCollapse this table
For all supported x64-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XPCollapse this table
For all supported IA-64-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XPCollapse this table
For all supported x86-based versions of Windows Vista SP2 and of Windows Server 2008 SP2Collapse this table
For all supported x64-based versions of Windows Vista SP2 and of Windows Server 2008 SP2Collapse this table
For all supported IA-64-based versions of Windows Server 2008 SP2Collapse this table
Collapse this table
Collapse this table
Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Properties | Article Translations |


Back to the top








