I've been using VSS6.0 at my new workplace for the last month and a bit now and at first was very impressed with the integration with Visual Studio with regards to Open from source control for a project which automatically pulled down the files in the solution (and child projects) and created IIS applications for all the web projects and placed everything in the same place as was originally set up.

I used to work in a Subversion environment where you could check things out manually and had to setup the IIS seperately. I've been using NANT for a while now and could quite happily write a script to pull down everything to get a dev environment setup.

There are problems with integration with VSS6.0 and VS2003 which have been highlighted by other ranting bloggers in the past such as Alan De Smet , Mark Levison and a lot more!

Microsoft have tried to come up with some standards on how to use VSS in a team environment.

My main concerns are with renaming files and it not renaming the files in VSS repository and creating two files. Also not deleting the files from the repository when you delete them from your Project in VS. I find the paradigm of Checking out a file (e.g. a code behind file) and it also checking out the aspx and the resx prevents a front end guy and a C# guy from working on the same thing at the same time. Subversion handles this a lot nicer with merging.

Also, if someone has the project checked out only one person can be adding and deleting files at the same time. I'd like to see how this works on a large project! I'd also like to see how this works offline and then when you try and reconnect!

I'm sure the new Team System works a lot better...but unfornately it is pretty expensive and needs a lot of servers etc. VS2005 doesn't seem to have changed too much either. The move now works and renaming seems a bit tidier.

Anyway... </rant>