[2008] choosing Subversion integration for Visual Studio

[trkl]

I'm going to migrate to Subversion (from SourceSafe), but I lack one feature I used to very much - VS integration. "A must" features for me - rename files and folders in repository when I rename them in Studio, and auto-add new files to repository.
After spending some hours in Google, I found these tools:
-Pushok SVN SCC http://pushok.com/soft_svn.php
-VisualSVN http://visualsvn.com/
-UnifiedSCC http://aigenta.com/products/UnifiedScc.aspx
(I found also AnkhSVN and TamTam SVN, but both of them look too buggy to use)
All them look usable at a glance, but they are commercial and I don't know which one is better, and what pitfalls can be here?

[bmahler]

SourceGear Vault is free for a single developer if it is just for yourself and it integrates with vs perfectly. I personally find it much better than SourceSafe.

[mendhak]

Does Team Foundation Server not do this?

[trkl]

Subversion does all I need to do. I only need advice which Subversion-VS integration software better to choose.

[Jumpercables]

VisualSVN is integrates nicely with Visual Studios but it's not free. It does have a hassle free trial period.

I would strongly suggest Tortise SVN which is completely free and integrates with Windows.

[trkl]

VisualSVN is integrates nicely with Visual Studios but it's not free. It does have a hassle free trial period.

I would strongly suggest Tortise SVN which is completely free and integrates with Windows.

TortoiseSVN is good, but renaming versioned files manually is real mess. So I need integration plugin in addition to it. Any info about other two plugins?

[trkl]

So far, my impressions about these plugin.

Pushok SVN is not an integration plugin actually, it only works as a proxy between SourceSafe plugin and real Subversion repository. Works slowly and has lots of limitations - not a good candidate.

Unified SCC (Aigenta, http://aigenta.com/products/UnifiedScc.aspx) and VisualSVN (http://visualsvn.com/) have the mostly similar functionality. Unified SCC also supports CVS and more IDEs than VisualSVN, but I only need Subversion and VS2008/2005 so it doesn't matter for me.
VisualSVN doesn't support multiple binding roots, that's bad for my tasks. VisualSVN works as VS integration package.
Unified SCC uses native VS source control integration via MSSCCI, this has it's own advantages and disadvantages.
Pro:
-works faster
-familiar interface (for those people, who used VS integration before)
Contra:
-Requires performing additional VS project-to-repository binding, it's not very intuitive and requires to read the manual (if you didn't work with VS source control integration before)

After all, I decided to use Unified SCC - it works better for me.