I have been trying to use VSS integration with VS.Net for well over a year.  It works great at home when I am by myself.  I can track changes and keep versions in history and can confidently change code knowing that I can roll back if I have to.  At work, however, when it is critically important, the integration has limitations that result in having to use VSS explorer outside of VSS.Net.

I have come to very few revolutionary conclusions.  I was hoping to get to a point where I could recommend a configuration for a large development team.  Unfortunately, I can only express that for those who wish to use it, VSS integration is tolerable.

First off, only bind what you will be editing.  If you aren't going to be changing a project that is part of a larger solution, get the files from source control and use them locally but don't bind them to the VSS location.  If you don't need the source code at all (for debugging or stepping through funtionality) simply get the binaries and use the compiled dll.  Its much easier and saves a lot of time when getting latest.

For a project that you do modify and require VSS functionality, here are some tips:

• Project should remain writable.  It is a pain in the butt to have to check the project out to remove a component from the project or to add a test page.  When you need to make persistent project changes, check out the project file externally, make your changes, check it back in, then mark the file writable again.
• In VS.Net, under tools --> options --> Source Control --> General:  check the box “Allow checked in items to be edited“
  now you can chose “edit“ in the Source Control dialog in addition to check out.  very useful when you want to add a simple message or line of test code but do not want to persist that change

That's all I have for now, if I think of anything else, I'll let you know.