KB936123 - TypeResolutionService sometimes uses incorrect active project

Article Translations
English, Français, Deutsch, Italiano, 한국어, 繁體中文, 简体中文, 日本語, Русский, Português (Brasil)

Description
A Hotfix is a product update package with one or more updated product files that fix a specific product problem.

IMPORTANT NOTE

Please be aware this Hotfix has not gone through full Microsoft product regression testing nor has it been tested in combination with other Hotfixes.

Please carefully review the associated Hotfix KB article to verify the fix is the one needed and there are no known compatibility or installation issues. You may also want to contact a Microsoft Support Professional at http://support.microsoft.com

Issue Description

KB936123 FIX: TypeResolutionService sometimes uses incorrect active project when resolving types through the AppDomain.AssemblyResolve



SYMPTOMS
KB936123: When you open a workflow by using the workflow designer in Microsoft Visual Studio 2005, you occasionally receive the following error message:
Error loading workflow

An error occurred while loading the workflow. Please correct the following error and try reloading the document to view the workflow.

The type initializer for 'Microsoft.Practices.PageFlow.WorkflowFoundation.Activities.PageFlow' threw an exception.
Note The workflow designer is a part of the Visual Studio 2005 extensions for the Microsoft .NET Framework 3.0 (Microsoft Windows Workflow Foundation). You must install the workflow designer separately. The workflow designer is not a part of the release version of Visual Studio 2005.


CAUSE
This problem occurs because the TypeResolutionService method sometimes uses the incorrect active project to resolve the types of the workflow in the AppDomain.AssemblyResolve event.

Additional Information about the issue resolved by this Hotfix can be found in its Knowledge Base article at http://support.microsoft.com/kb/936123

Additional Hotfixes
Search the list of all other publicly available Visual Studio and .NET Framework Hotfixes at http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix&ProjectSearchText=Hotfix*