Source Control: VisualSVN, TortoiseSVN, AnkhSVN question

I have just started working with another developer on a team. Prior to working together we both built small in house applications individually. So anyway one of the first things we had to do as a team is start using some kind of source control.

I have downloaded and installed VisualSVN, TortoiseSVN, AnkhSVN and everything seems to be working fine with our limited use of it. However I suspect that there is a lot to know about using inside Visual Studio that isn’t necessarily obvious with trial and error method that we used to get started so I was wondering if anyone knew of a good "beginners" article that covers using those tools together as source control in VS?

Hmm, question that doesn't answer your question - if using Visual Studio, why not use Team Foundation Server/Team Explorer?

Small shop and code is only part of what we do so we can't really justify the cost of it right now.

I would love to use TFS but it's very expensive for small shops.

VisualSVN is very good. I've had good experience with it as well as TortoiseSVN. AnkhSVN, however... well, it's kind of hacky as it adds its own sub menu to Visual Studio rather than using the predefined Check-in, etc functions which always seemed odd to me but I'm not aware of a better tool.

Vault is pretty nice and you may want to check it out but it requires more hardware as it uses SQL Server and recommends at least 1GB of ram.

We use TotoiseSVN here, its a really handy ShellExtension and we have around 3-8 developers using it.

Pino

At one of jobs we use zip files and a network share (a very poor system, I'm trying to get them to use a source control program) at my other job we use Visual Source Safe for the .net developers and SubVersion for the java developers

Here is the tutorial that I used to setup my source control Source Control for Visual Studio 2008: VisualSVN Server, TortoiseSVN, & AnkhSVN. I have never used the others so I cannot offer a comparison of features. I can say that does exactly what I needed it to do and it didn't cost me anything other then about an hour of time to set it up and apply some trial and error learning to its use.

i used to use SourceSafe with no issues whatsoever, new job uses SVN and to be honest its a heap in comparison

Visual SourceSafe 2005 is the last version MS will produce of it. Its going to be replaced by TFS Express or such. I cant remember what the exact name was but its a lite version of TFS.