FIX: The Copy Project feature in Visual Studio .NET 2002 fails when you copy to a share when the trailing virtual root path does not match the virtual root alias

Notice

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
If you use the Copy Project feature by using the FileShare method in Microsoft Visual Studio .NET 2002, the feature may not work when you copy between two computers that are on different domains.

Note You can use the Copy Project feature with two computers that are on different domains by using Microsoft FrontPage without errors. You can also manually copy the project to the remote server by using the Universal Naming Convention (UNC) path.

You may receive the following error message when you use the Copy Project feature to copy a project from a computer that is on one domain to a computer that is on a different domain:

Unable to create web project 'ProjectName'. The UNC share '\\ShareName\ProjectName"' does not exist or you do not have access
CAUSE
This problem occurs because the path that the project is copied to does not match the path from the source destination. The trailing virtual root path must match the virtual root alias. For example, if you create a virtual root that is named MyVRoot, the folder that it maps to must have MyVRoot as the trailing folder name. In this example, the folder must be c:\MyVRoot or c:\FolderName\MyVRoot. If you are copying a project to a remote share, the virtual root must be at least two levels below that share. For example, \\Server1\ShareName\SubFolder1\MyVRoot. You must have the SubFolder1 folder or another intermediate folder).
RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft 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

Software update information

Prerequisites

The .NET Framework 1.0 Service Pack 2 (SP2).

File Information

The English version of this software update 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   -------------------------------------------------------------------   03-Feb-2004  13:31  7.0.9763.0    917,504  Csproj.dll   03-Feb-2004  05:03  7.0.9763.0    176,128  Csprojui.dll   03-Feb-2004  13:11  7.0.9763.0    311,296  Dirprj.dll   03-Feb-2004  13:26  7.0.9763.0  1,400,832  Msvbprj.dll   03-Feb-2004  05:02  7.0.9763.0    180,224  Msvbprjui.dll   03-Feb-2004  06:41  7.0.9763.0    253,952  Visualstudioteamcore.dll   03-Feb-2004  06:39  7.0.9763.0    888,832  Vsavb7dt.dll   03-Feb-2004  06:39  7.0.9763.0    999,424  Vsavb7rt.dll   03-Feb-2004  06:40  7.0.9763.0    794,624  Vsavbproj.dll   03-Feb-2004  13:30  7.0.9763.0  2,981,888  Vsscc.dll   03-Feb-2004  13:11  7.0.9763.0    311,296  Dirprj.dll   03-Feb-2004  06:41  7.0.9763.0    253,952  Visualstudioteamcore.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.
Properties

Article ID: 833552 - Last Review: 01/17/2015 05:47:37 - Revision: 2.3

  • Microsoft .NET Framework 1.0
  • Microsoft Visual Studio .NET 2002 Enterprise Architect
  • Microsoft Visual Studio .NET 2002 Enterprise Developer
  • Microsoft Visual Studio .NET 2002 Professional Edition
  • Microsoft ASP.NET 1.0
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbvs2002sp1sweep kbvs2002sp1fix kbqfe kbnetframe100presp3fix kbdevstudio kbfix kbbug KB833552
Feedback