FIX: You may receive multiple error messages and experience a significant delay when you use the MSBuild.exe tool and the .NET Framework 2.0 to build a Visual C# or Visual C++ solution

This article has been archived. It is offered "as is" and will no longer be updated.
When you build a Microsoft Visual C# or Microsoft Visual C++ solution that contains many projects, you may receive multiple error messages that resemble the following:
Sample1.dll : warning C4945: 'LogicalThreadContextProperties' : cannot import symbol from 'Path\Sample1.dll': as 'Sample1::Util::LogicalThreadContextProperties' has already been imported from another assembly 'Sample1'
These error messages do not prevent the build process from completing successfully. However, the error messages cause a significant delay in the build time.In some cases, the build is delayed up to several hours.

You may experience this problem when you use the MSBuild.exe command-line tool and the Microsoft .NET Framework 2.0 to build the solution.

You do not experience this problem when you use Microsoft Visual Studio 2005 to build the solution.
This problem occurs because the Copy Local property on one or more of the referenced assemblies or projects is set to True.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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 .NET Framework 2.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

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.
File nameFile versionFile sizeDateTimePlatform
To work around this problem, set the Copy Local property to False.

Note In some cases, setting the Copy Local property to False does not fully resolve this problem. In those cases, you must install the hotfix that is described in the "Resolution" section.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the MSBuild.exe command-line tool, visit the following Microsoft Web site:

Article ID: 922271 - Last Review: 01/17/2015 15:21:36 - Revision: 3.0

  • kbnosurvey kbarchive kbexpertiseinter kbqfe kbhotfixserver kbbug kbfix KB922271