FIX: "Directory eoes not have write permissions" error message when you add files to the remote root (324487)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2002), Academic Edition
This article was previously published under Q324487 SYMPTOMS When you create a new Web project and then try to add a new
file to the project, you receive the following error message:
Directory does not have write permissions You
receive this error message under the following circumstances:
- You create the new Web project by connecting to the root
Web on a remote server. -and-
- You use the File Share access method (which is the
default). -and-
- You add files with any of the following extensions:
- .asax
- .ascx
- .asmx
- .aspx
- .config
- .cs
- .xsd
Note This problem does not occur when you add other file types (such
as .htm files, .xml files, and .css files) to the project. Additionally, this
problem does not occur when you connect to the local computer. RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Micorsoft Visual Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
837234 List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1
Hotfix information
The English version of this fix 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
----------------------------------------------------
19-Jun-2002 15:20 7.0.9510.0 294,912 VsWizard.dll
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbvs2002sp1sweep kbvs2002sp1fix kbbug kbfix kbQFE KB324487 |
---|
|