All of these solutions setup the standard Apache HTTPD server with Subversion integration. They do no real magic.
UberSVN and VisualSVN provide a pretty front end interface, but behind the scenes, it's just standard Apache setup. If you are not a CM, and don't want that to be your job, that's not a bad alternative. However, do not ever try to tweak the configuration behind their backs. They will either revert the changes, or really mess things up.
However, I use Apache httpd in order to access my Windows Active Directory. I setup my users, so their Windows account and password are their Subversion account and password. I setup a Active Directory Security Group or a Active Directory Exchange Group as my authorization database. If a user is a member of this group, they have access to the repository via their Windows login. If not, they don't have access. Clean and simple. I am no longer in the user authorization business which gives me more time to
play Candy Crush ..I mean.. other CM work.
Otherwise, I might as well just use
svnserve: It's faster than Apache httpd, much easier to setup, and more stable too.
If you're not going to use Active Directory as your authorization backend, you are technical, and don't mind getting your hands a bit dirty, I would use either play
svnserve (and set it up as a Windows Service. No need for any of these packages.
If you are going to use Active Directory as your authorization backend (and why not?), I would use CollabNet Subversion Edge to help setup Apache httpd and Subversion and do all of my configuration manually. Setting up Active Directory via LDAP via Apache httpd isn't really that difficult, and once done, you probably never have to touch again. The documentation on integrating Apache httpd/Subversion/LDAP/ActiveDirectory can easily be found.
I suggest you look at the on line Subversion Documentation and go through it. If thinking about using the
svn command line client makes you woozy, then get VisualSVN or UberSVN and let them take care of things for you. If you don't mind going all 1990 with your computer, then forget about the pretty front ends, and use CollabNet Edge.
One more thing, I am not a fan of ViewVC that comes with CollabNet Edge. It has to use
file:// protocol and must run on the same server as your Subversion server software. Instead, I prefer Sventon. It can run on a separate server, and you can use the same credentials as your standard Subversion credentials. Plus, I like the interface a bit better.