This article was previously published under Q326403
This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft Visual Studio .NET 2002, when you rebuild a solution you may receive the following error message:
Could not delete file File Name. Make sure that the file is not open by another process and is not write-protected.
Note In this error message, File Name is a placeholder for the path and the name of a .dll file.
When this problem occurs, you must restart Visual Studio .NET before you can rebuild your solution.
This problem occurs if the Read-only property of a .dll file from an earlier build is set to true. The read-only property of a .dll file is set to true when the GetAssemblyName method is called to get the name of an assembly.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, 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.
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 tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------------- 11-Jul-2002 07:10 1.0.3705.295 65,536 Fl_corperfmonext.dll 12-Jul-2002 18:25 1.0.3705.295 1,953,792 Fl_mscorlib.dll 11-Jul-2002 07:09 1.0.3705.295 2,265,088 Fl_mscorsvr.dll 11-Jul-2002 07:02 10,256 Mscorlib.ldo 11-Jul-2002 07:09 1.0.3705.295 2,265,088 Mscorwks.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the terminology that is used to describe Microsoft product updates, 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