Article ID: 831649 - View products that this article applies to.
When Microsoft Visual Studio .NET opens a Web project, Visual Studio .NET tries to use one cache location for all URLs that appear to be the same. For example, the URLs http://localhost, http://localhost:80, http://localcomputername, and http://220.127.116.11 all locate the root folder of the Web server on the same local computer. Visual Studio .NET tries to use one cache location that has the name of the local computer for all these URLs.
The problem occurs if the computer has more than one IP address and each Web site uses a separate IP address. The reverse lookup to obtain the computer name returns the same name for each IP address. Therefore, all the Web sites that use IP addresses on the same computer share the same offline cache location. This behavior may cause data loss and other related problems.
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 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:
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 -------------------------------------------------------- 04-Nov-2003 23:20 7.10.3308.0 200,704 Cmddefui.dll 04-Nov-2003 23:06 7.10.3308.0 598,016 Bcaut.dll 05-Nov-2003 03:15 7.10.3308.0 1,015,808 Csproj.dll 05-Nov-2003 02:57 7.10.3308.0 327,680 Dirprj.dll 04-Nov-2003 23:45 7.10.3308.0 999,424 Esproj.dll 04-Nov-2003 23:20 7.10.3308.0 86,016 Msenvmui.dll 04-Nov-2003 23:45 7.10.3308.0 1,490,944 Msevbprj.dll 05-Nov-2003 03:07 7.10.3308.0 1,437,696 Msvb7.dll 05-Nov-2003 03:08 7.10.3308.0 1,507,328 Msvbprj.dll 05-Nov-2003 03:10 7.10.3308.0 827,392 Vbaproj.dll 04-Nov-2003 23:29 7.10.3308.0 1,036,288 Vjsproj.dll 05-Nov-2003 02:53 7.10.3308.0 913,408 Vsavb7dt.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 831649 - Last Review: October 25, 2005 - Revision: 2.6