Microsoft Knowledge Base Email Alertz

KBAlertz.com: (843370) - Dependent DLLs are locked when building after doing a Get Latest from Visual SourceSafe. Discusses a hotfix to correct this problem.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 843370 - Last Review: May 15, 2006 - Revision: 2.2

FIX: "Cannot copy assembly" error message during the build process after you use the Get Latest command to retrieve solution files from Visual SourceSafe

On This Page

SYMPTOMS

If you build a Microsoft Visual C# .NET solution after you have used the Get Latest command to retrieve the solution files from Microsoft Visual SourceSafe, you may receive the following error message when you build the solution:
Cannot copy assembly 'Referenced Assembly' to file 'Current Project Output Folder\bin\Debug\Release\Referenced Assembly.dll'. The process cannot access the file because it is being used by another process.
This error causes the build to fail. The error message means that the referenced assembly is the output of another project in the solution.

CAUSE

The problem occurs because the file that contains the referenced assembly is locked by another process. The IDE opens a handle to the file and then does not close the handle as expected. Therefore, the IDE cannot update the file. This file will remain locked until you restart the development environment.

It is a good idea to verify that you are not building all your assemblies to the same output directory. For additional information about conditions that may cause dependent DLLs to be locked during a Microsoft Visual Studio .NET build, click the following article number to view the article in the Microsoft Knowledge Base:
313512  (http://kbalertz.com/Feedback.aspx?kbNumber=313512/ ) BUG: "Could not copy temporary files to the output directory" error message when you build a solution that contains multiple projects

RESOLUTION

Hotfix information

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 Microsoft Visual Studio .NET 2003 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:
http://support.microsoft.com/contactus/?ws=support (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.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time  Version      Size     File name
   ------------------------------------------------------
   02-Jun-2004  8:37  7.10.4154.0  794,624  Cslangsvc.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft Visual C# .NET 2003 Standard Edition
Keywords: 
kbqfe kbbug kbfix kbvsnet2003presp1fix kbhotfixserver KB843370
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Corbin Hoenes - choenes NOSPAM-AT-NOSPAM henryschein.com Report As Irrelevant  
Written: 3/6/2005 9:06 PM
We need this fix to be released publicly. We have 10+ developers having this issue and the only way we can fix this is to get the patch or move to another source control system. It's ridiculous that Microsoft hasn't released ANY updates for VS.NET 2003.

Anonymous User Reported as Irrelevant  
Written: 9/15/2005 1:41 AM
Partial information is harmful that none info. so try to get in the detail other wise not

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please