I've used VS with Visual SourceSafe integration, and I've used VS with TortoiseSVN in a separate Windows Explorer window. The latter is so much easier to live with it's hard to begin describing it. TortoiseSVN is so straightforward I've never felt the need to figure out how to integrate SVN with VS.
But there are two pretty significant issues about using non-integrated source control.
The first is that when you add a new file to a project, you have to add it to SVN as a separate action. Without VS integration, you can't tell (by looking at Solution Explorer) that you haven't done this yet. This is pretty dangerous.
The second is that importing a project into SVN is really clumsy. There's two ways to do it and they both suck. I'd presume that a decent VS integration would make this a one-button operation.
(How to import a project with TortoiseSVN: Make a copy of your project directory called projectName.import. Delete every file from that directory tree that you don't want source-controlled, like everything in the bin directory. Import it into SVN and then throw away projectName.import. Rename your project directory as projectName.original. Create a new directory called projectName. Check your project out into that directory. Build and test. Once you're comfortable that everything's really in SVN you can throw away projectName.original.)
I've learned to live with both of those problems. Also, since I don't have SVN integration in Eclipse either, it means that I've only had to learn one thing instead of three.