Skip Navigation LinksHome > SSW Standards > Better Software Suggestions > Source Safe

1. Could VSS have the backend on SQL Server?
2. Could there be a backup and a restore option somewhere?
3. Could VSS be faster over VPN?
4. When comparing differences (with Diff) between two versions, you will be able to edit in place
5. It will automatically merge offline edited files
6. VSS needs to able to accept connections over the Internet
7. Update File Dialogs
8. VSS will be scalable
9. Links

  1. Could VSS have the backend on SQL Server?

    2. This would speed up data access.

  2. Could there be a backup and a restore option somewhere?

  3. Could VSS be faster over VPN?

    4. Why is it so slow at the moment over VPN?

  4. When comparing differences (with Diff) between two versions, you will be able to edit in place

  5. It will automatically merge offline edited files

    6. It will automatically merge offline edited files. Currently when you come back onto the network it doesn't merge, insteadit asks "Which file do you want to keep?". eg. If you edit one function online and edit another function one offline why not just merge them?

  6. VSS needs to able to accept connections over the Internet

  7. Update File Dialogs

    8. The file dialogs are very old and badly need an update. Currently even UNC's are time consuming to access.

  8. VSS will be scalable

    9. Microsoft Visual Source Safe 6.0d (VSS), the version control system for Visual Studio .NET, works just fine on small projects. However, when doing enterprise-level projects where you may have to pass up to 10,000 lines of code and have 10 simultaneous users, SourceSafe can have trouble scaling.

    Until Microsoft makes a version of SourceSafe that works with SQL Server, we have to rely on alternative, 3rd party tools for source control.

    Alternatives include:

    • SourceGear Vault
    • PerforcePerforce no good because it has a terrible cryptic
    • StarTeam
    • Source Integrity

  9. Links

 

Acknowledgements

Adam Cogan