We switched from VSS6 to VSS2005 a little over a year ago. The database structure is identical. The only caveat we discovered was that some people still used VSS6 in a database where others used VSS2005. VSS2005 considers Unicode text files as text files, while VSS6 does not. This means that when VSS2005 adds a Unicode text file, VSS6 treats it as binary (this applies to csproj files among others).
In addition, VSS2005 supports proper HTTP access to the database (provided that the server extensions are installed), improved local network performance (again with server extensions) and improved file system dialogs (the nasty old ones disappeared). However, the dialog box for adding a new file displays ALL files, and not just those that are not included.
In addition, VSS2005 allows you to provide custom editors and explode tools with a file extension, which is very useful. For example, some of our XML files are encrypted, so we run the decryption tool to the difference tool using this system, which greatly improves the efficiency of our browse processes.
There are other tricks here and there, mostly good, but sometimes annoying.
Finally, nothing was destroyed. Actually, it seems that there was less corruption in the database than the transition, but I would not use this new VSS, as it was not a comprehensive test.
Jeff yates
source share