#Visualsvn series

WeвЂ™ve broken this series of tutorials down into the following five parts: And itвЂ™s working with SVN, Visual SVN server and Tortoise SVN that weвЂ™ll be looking at over the next five tutorials. However, being a command line tool doesnвЂ™t make SVN particularly easy to work with so the Visual SVN tools were developed to help people like you and me work with SVN. ItвЂ™s issues like this that SVN was designed to solve. but both version 2вЂ™s of the file are most likely different. And your colleague has version 2 of the fileвЂ¦.

#Visualsvn update

At the same time though you update your version 1 of the file on your local system. You send this in an email to your colleague and he/she updates it to version 2. You have a single file on your computer and that file is at version 1. The worst bit though is that youвЂ™ve copied it back and overwritten my changes. Then shortly after you copy your version of the file back to the server. I copy version 2 of the file back to the server so that itвЂ™s available for everyone else to look at an update. At the same time, you take a copy and update it. I take a copy of this file and updated it. So, for example, you have a single file on a server and that file is at version 1. The complexity starts to come when you what to combine both concepts and start having more than 2 or 3 people working on the files. We can achieve this by either sending the file round in emails as an attachment or having the file on a shared file system where many people have access to this one file.Д«oth of these concepts in their own right are a simple concept that is easy to implement and easy to work with. When we collaborate on files all weвЂ™re looking for is the ability to share a file and for two or more people to be able to update that file. If we want to go back too our original version we just open the вЂfirst versionвЂ™ of the document. We make changes and save a copy of the file as the вЂњsecond versionвЂќ. It just means we want to have a file that starts out as the вЂњfirst versionвЂќ. Version control of files is a simple concept in its own right. LetвЂ™s just go back to the main features of a version control system for a second. Tortoise SVN: the client application called Visual SVN, that allows you to manage your files locally, get your files from the server and commit your updated files to the server. Visual SVN Server: a server applications, the central repository that holds all the files you want to version control, called Visual SVN ServerДў. WeвЂ™re just using Visual SVN Server and Tortoise SVN client because they are quickest and easiest ways to use SVN and start learning about SVN. Then we have an independent Open Source project (GPL) called Tortoise SVN that provides a client front end for windows.

#Visualsvn software

Separately to this, a company called VisualSVN Software Ltd have developed an SVN server application that works as a graphical front ends to the SVN server component.

#Visualsvn code

The home of SubVersion is the Apache Org Subversion website where you can download the source code (youвЂ™ll find many mirror sites that host the binaries for various platforms). ItвЂ™s open source project and is predominately a command line tool (both for Windows and Unix). SVN has been developed by CollabNet and is currently maintained by the Apache Software Foundation. Add to this a graphical user interface called вЂњTortoise SVNвЂќ and this gives us the simplest and quickest way for individuals to collaborate on files and version control those files. SVN deployed with Visual SVN Server gives us a server environment within which to maintain our files. That is, itвЂ™s a tool that allows us to version control files and collaborate on files. Subversion (from here on in referred to as SVN) is a centralized Version Control System. In this set of tutorials, weвЂ™re going to take you through the basics of Subversion with Visual SVN Server and Tortoise SVN.