Article ID: 199035
Article Last Modified on 8/12/2005
APPLIES TO
- Microsoft Visual SourceSafe 6.0 Standard Edition
- Microsoft Visual InterDev 6.0 Standard Edition
- Microsoft Visual Studio 6.0 Enterprise Edition
This article was previously published under Q199035
SYMPTOMS
When adding a Visual Studio solution (.sln file) that contains a Web project to Visual SourceSafe (VSS), the .sln file and the project files are added to different VSS databases.
CAUSE
The .sln file and the Web project use different mechanisms for SourceSafe integration. The .sln file uses the same mechanism as other Visual Studio components, such as Visual Basic and Visual C++. Visual InterDev uses the FrontPage Server Extensions (FPSE), which in turn interact with VSS through OLE automation. This mechanism determines which database the Web files are added to. It is important to note that all VSS operations on the Web files are done on the IIS server machine, not on Visual InterDev clients.
RESOLUTION
To resolve this problem, first identify which VSS database is being used by FPSE, then ensure that the .sln file is added to that database. For most users the best option will be to create a workstation installation of VSS on the client machine by running VSS's netsetup from the database used by the Internet Information Server machine.
STATUS
This behavior is by design.
Keywords: kbprb KB199035