This article has been archived. It is offered "as is" and will no longer be updated.
If two Web sites are created on the same server, and the two Web sites have the same IP address, the same port, and the same host headers, and if one of the Web sites is always offline and the other Web site is active, you may experience problems when you try to connect to these Web sites.
In Microsoft Visual Studio 6.0 or in Microsoft Visual Studio .NET, you may be able to connect to these Web sites by using one solution file. However, Visual Studio or Visual Studio .NET always tries to connect to the last Web site that was found in the metabase that matches the solution.
If the Web site that Visual Studio or Visual Studio .NET tries to connect to is offline, you receive an error message that states that Visual Studio or Visual Studio .NET cannot connect to the site. The error message contains the Universal Naming Convention (UNC) location of the second site.
This hotfix causes Visual Studio .NET 2003 to connect to the active Web site and to ignore the offline Web site.
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:
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) 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-Dec-2003 06:19 7.10.3353.0 200,704 Cmddefui.dll 19-Dec-2003 09:44 7.10.3353.0 1,015,808 Csproj.dll 19-Dec-2003 09:26 7.10.3353.0 327,680 Dirprj.dll 19-Dec-2003 06:19 7.10.3353.0 86,016 Msenvmui.dll 19-Dec-2003 09:37 7.10.3353.0 1,507,328 Msvbprj.dll 19-Dec-2003 06:31 7.10.3353.0 1,036,288 Vjsproj.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional 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