Title page

SNV Tool and the VisualSVN

Name
Institution

Introduction

SNV is one of the Subversion controls tools. Subversion Controls allows

large project managers and programmers to work on the same projects
while approaching it from diverse angles and not hindering each others
operations.

Additionally, the Subversion helps in saving man-hours used in paperwork

coding and notes associated with programming.

The term SNV refers to a system through which different users can share
information from a centralized source. The system has a central store where
data is stored called a repository

Contd

The SNV is able to track changes made to files and directories and manage
these changes as they are made over time. Through this, one can track
changes effected on data, who made the changes and how. By so doing,
recovery of older versions of the same data is possible through the SNV.
Since the Subversion has the ability to operate across networks, various
computers can use it simultaneously or concurrently.

Collaboration among and between users is possible especially when

different users can work on the same data and manage it from different
locations. SNV can control various collections of files ranging from source
code to shopping lists in a grocery and many others. (Collins-Sussman,

Fitzpatrick, & Pilato, 2008).

Key benefits of SVN

The key advantages of SNV over basic server file sharing are that
various users can work on the same file at the same time. In addition,
user can track changes made to data, where, when and by whom.

Integrating changes to a file in the repository is possible and therefore

users can do this to their copies. The main shortcomings include
reduced comparative speed, there are bugs that relate to renaming
directories and files, and it has few repository management commands
(Collins-Sussman, Fitzpatrick, & Pilato, 2008).

Specific VSN: VisualSVN

This tool enhances the version control for clients involved in development of Visual
Studio. The VisualSVN operates on the concept and principle of transparent
subversion where it indicates all the daily developments from Visual Studio cycle
and the actions done on the subversion automatically. For instance it marks all added
files and directories as added. As such, developers are able to pay attention to
development while the VisualSVN tackles the versioning aspects (VisualSVN, 2008).

In addition, one is able to work on files in the Solution Explorer transparently. Such
operations as copying, addition, deletion, drag and drop, and renaming are supported
by VisualSVN in a transparent manner which saves users agony in refactoring.

VisualSVN contd

The VisualSVN conveniently duplicates the entire effects on the

working coping copy on a position that is easy to identify usually the
right corner of the status bar of the Visual Studio. There are other
unique capabilities of the VisualSVN like accessing all Subversions
command in a convenient manner using the stable and mature GUI of
TortoiseSVN; which is the default standard Subversion used by the
Windows platform. This way one is able to get both Windows Explorer
and the Visual studio access in unison (VisualSVN, 2008).

Conclusion
VisualSVN

integrates the Subversion to

the environment of Visual Studio
development professionally.
Its capabilities meet all the necessary
needs of software development process
such as addition, refactoring, merging,
and branching.

References
Collins-Sussman,

B., Fitzpatrick, B. W., &

Pilato, C. M. (2008). Version Control with

Subversion for Subversion 1.5 (Compiled
from r3305). Ben CollinsSussman, Brian W.
Fitzpatrick, C. Michael Pilato, c2008,
Modified: Mon, 5, 08.
VisualSVN,

(2008). Subversion integration

for
visual studio.
Retrieved 8th May 2015
from
https://www.visualsvn.com/visualsvn/doc/
Visua lSVN.pdf