The original thrust of the discussion was source code control vis-a-vis LabVIEW source files, but something to bear in mind when choosing/deploying a versioning system is that projects typically consist of lots of different types of files, and nearly all of those files can benefit from version control. That's why it has never really bothered me that SVN/TSVN doesn't integrate with the LabVIEW project environment. I see it as a tool for managing all my project-related documents, not just source code. If virtually every file I use for project work can benefit from versioning, then I should have an ex-LabVIEW versioning workflow in my head anyway. I don't feel like I need the process duplicated in the development environment.
In fact, a friend of mine in a totally unrelated field actually used Subversion & TSVN to manage all the revisions of his Master's Thesis and related support documents. The only thing he knows about source files is that they end in things like .c, .h, .vi, etc. and that he never wants a job where he has to touch them
.Other Notes: Even back when I was operating independently, TSVN performed beautifully for me even as a single developer (with an occasional assistant or collaborator). Even the threat of merge conflicts just forces clear communication between developers, which is a very good thing. What's more, Subversion/TSVN are pretty light-weight, so it was always a snap to install them on a customer's computer to do a project checkout on-site when necessary.
