I developed a wrapper class for Sourcesafe 6.0d which has functioned perfectly for months now. I recently installed Beta 2 to begin porting stuff, but when I run my old VSS wrapper code and get it to check in items it performs very slowly. So I started to investigate just using VSS itself. I checked things out that visually in VSS did not appear to be checked out, but VSS gave an error saying items being exclusively checked out. When I refreshed some items had been checked out and others had not.
I bulk checked in items with my wrapper, and although the items no longer appeared to be checked out, they were not checked in, as I did a diff and the files were different.
Can anybody please tell me definitively if they are experiencing the same problems. Please don't tell me about not installing beta products etc. This is the real world, where side by side installations will have to be made in real life environments and assertions have to be made about the coexistence of different product versions.
Regards,
VSS6.0d erratic behaviour after installing VS 2005 beta 2
Hot Topic
- Is there a Native C++ API?
- Outlook Winform
- Advice on installing Visual Studio 2005 Professional and SQL Server 2005 Developer
- "Reload" listobject after UnList()
- C++ File Dependencies
- Error: "data\rights.dat is already open"
- Error in installikng Windows SDK
- VSTS - Web Test - FIND TEXT command
- How can we Trace and log the WCF Service Messages?
- DLinq and null values and defaults
Visual Studio
- Change name of Extension & name of the language afterwards
- WCF Feb CTP/Windows SDK - InfoCard Sample
- Unable to unregister the AddIn
- ComboBox bug
- Debugging BackgroundWorker threads
- VSS 2005 - Install - Missing Menu Items in VS 2005
- Project Subtype from wizard
- WinFx - Convincing Clients to buy into it ?
- Send email using Outlook
- Any Practical Limits on Model Size?
VSS6.0d erratic behaviour after installing VS 2005 beta 2
sebepsiz
I don't know what's causing your problems, but it may be possible you have some database corruption (it sounds strange that you get error messages that files are exclusively checked out when they aren't visually checkedout in VSS Explorer)
I'd try running analyze on the database
Also, note that VSS 6.0d and VSS2005 are not 100% side-by-side.
While stand-alone binaries like SSexp/SSadmin can be run side-by-side, using VSS integration in VisualStudio is not SxS (last ssscc.dll registered wins). Also, using IVSS automation interfaces is not SxS when used from products like VB6 (when using from VB8 make sure you have in project the reference to the right version of the VSS typelib).
Alin