Minimal Set of Rules for Team Development with Visual Studio.NET and VSS
I'm trying to pare this down to just the absolute streamlined minimum, here's what I have so far. If you have comments, feel free to contribute: Minimal rules for Team Development: 1) Learn how to add a solution / project to VSS and make sure you don't screw up. Everybody needs to be able to be working from the same solution tree, and a new developer should be able to get latest on a solution and successfully build it within 10 to 20 minutes. Shared library references should be in the solution as Solution Items, and they should be able to be checked out with the Solution. If a shared library needs to be changed, it should be checked out and the new library saved over it, then checked back in so everybody can have the same versions. 2) All references should be PROJECT references if the project is available, and the project should be retrieved from VSS and included in your solution. 3) All build output from EVERY project should go ONLY into it's respective /bin folder...