FIX: Visual Studio .NET 2002 breaks Visual SourceSafe integration behavior (319997)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual SourceSafe for Windows 6.0
This article was previously published under Q319997 SYMPTOMS The Visual Source Safe (VSS) integration behavior in Visual
Studio .NET 2002 is different from that in Visual InterDev 6 (VID6). In VID6, the
files are always automatically checked out when they are copied and pasted into
the IDE if the targets already exist and are replaced by the source. In Visual
Studio .NET, this is not the case.
NOTE: Always use the Get Latest Version command for the whole project before you add files or check in
changes from the Visual Studio .NET IDE. RESOLUTIONService 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
Hotfix information
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
-----------------------------------------------------------------------
25-Jul-2002 19:35 7.0.9522.0 917,504 Csproj.dll
25-Jul-2002 19:15 7.0.9522.0 311,296 Dirprj.dll
25-Jul-2002 19:29 7.0.9522.0 1,400,832 Msvbprj.dll
25-Jul-2002 16:07 7.0.9522.0 253,952 Visualstudioteamcore.dll
25-Jul-2002 19:33 7.0.9522.0 2,981,888 Vsscc.dll
25-Jul-2002 08:39 7.0.9522.0 176,128 Csprojui.dll
25-Jul-2002 08:38 7.0.9522.0 180,224 Msvbprjui.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio .NET
2002 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 1/20/2006 |
---|
Keywords: | kbvs2005doesnotapply kbvs2005swept kbHotfixServer kbvs2002sp1fix kbvs2002sp1sweep kbbug kbfix kbQFE KB319997 kbAudDeveloper |
---|
|