Learning to use source control
Let's look at some guidelines on how to use source control in a (remote) pair programming context. Some people might even enforce these guidelines and call them rules, making them part of the coding guidelines of the team. The most important thing is that the team understands why it's important to respect these guidelines.
Source control tools
Like any programmer, I have some favorite tools. Yours may be different, and that is fine. I want to explain why I use a distributed source control, and why I would never go back to centralized source control.
When I started programming, we were using these tools such as CVS, SVN, and Source Safe to manage code contributions. There were many teams who didn't have any source control, and I always found that scary. From the start, using Source Safe didn't feel safe at all. It would lose files and references, and it was never a reliable tool. CVS was complicated to use; you needed a lot...