I tend to use TortoiseSVN both at home and at work as my primary subversion tool. No matter how good any VS revision control can be I feel that Explorer integration will always be required as, after all, we are dealing with files. Also, TortoiseSVN's ability to be configured to require a bug ID (ala story ID) is essential in some work environments. So any VS subversion integration tool that integrates with TortoiseSVN is leveraging off TortoiseSVN's functionality that you would be using anyway. Big win.
Also, even after a few hours of use, VisualSVN provides many other very useful benefits:
- Files moved in VS are shown in commit as "Add(+)" and history is maintained.
- Tortoise options accessible via VisualSVN menu in Visual Studio.
- File modified indicators visible in solution explorer as you would expect.
- Modified files in VS status bar is very useful. I often want to know if a box has any changes and this little indicator gives me instant indication.
- 'Show Changes' menu option within VS very useful.
- Changed line are highlighted in VS editor pane. Impressively, still only shows changed lines on a moved file, that is no line changed if not edited before/after move.
- VS tool bar buttons for commit, update, show changes.
- Full synchronization with Tortoise actions outside of VS. e.g. Files added to subversion using TortoiseSVN outside of VS, without commit, show up in VS immediately.