Download the CollabNet Subversion Server and client for Windows from http://www.collab.net/downloads/subversion - you will need to create an account to do this, but don't worry, registration on CollabNet is free, and they won't share your e-mail address with anyone.
Run the installer, and follow the on-screen instructions. As we want SVNServe only, deselect the Apache(MOD_DAV_SVN) option and click Next.
Ensure that the Install svnserve to run as a Windows service option is checked. For most people, the default Port is OK. Choose a Repository Path which matches the path you created for your repositories in the previous "Time For Action". In the case of Shiny Moose Software, the default path is correct.
In most cases, the options on the Automatic Updates screen can be left at the defaults. If you use a proxy to connect to the internet (which is unlikely, unless you are installing the server in an office environment), then tick the relevant box, and fill out the proxy details when prompted.
Finally, click Finish.
We have just set up a simple SVNServe-based Subversion server. At the moment, we can't do much with the server. It allows anonymous read access, but no write access. That means it's great for letting people download our code, but not so useful for letting people submit any changes they decide to make.
We could allow anonymous write access – but that wouldn't really be a good idea – after all, what's to stop a competitor, or simply a mean-spirited person, from changing our code? Also, how will you know which member of your team submitted which changes? Giving each user of your repository a username makes it a lot easier to track who is doing what, and also to restrict what each person can do. Instead of allowing anonymous write access, let's set up some simple authentication, so that we can control who can and cannot edit our code.