So far, there have been manySource codeManage the application software. Among them, products, open-source, and cross-platform products are superior to each other, and I believe they have all been used clearly.
In the previous article, I made some comparisons. For details, refer to the comparison of SCM tools such as VSS, CVS, SVN, and clearcase.
The source code management system I first came into contact with was Microsoft's VSS. It was easy to configure and get started, but it was very weak in terms of security. Later I basically didn't need it. Then we came into contact with CVS, and the unique features were quite impressive. Then begin to contact SVN. But at that time, SVN was from Apache+ The SVN application mode is not used. Later, I found the svn solution in windows. The following is an introduction.
Two products are available on the http://www.visualsvn.com of visual SVN server. One is visualsvn, and the other is visualsvn server (hereinafter referred to as server ). The former is a plug-in integrated into Visual Studio, which has powerful functions, but requires a low cost. The latter is the svn server-side system we will introduce. On the Server Download Page, we can seeIncludes subversion 1.6.1From this we can know that it is the originalSubversion +Apache mode is an encapsulation that makes it easier to use.
The latest version is 1.7.1. Visual SVN server 1.7.1
The installation of visual SVN server is simple. An important step is shown in:
The repositories should be changed to another disk directory for storage, not to mention the specific reason (according to the actual installation,ProgramPath and repositoryCodeThe path must be in the same drive letter; otherwise, installation may fail due to service startup failure, which is a strange problem ).
We also recommend that you check the usesecure connection item. At this time, only ports 443 and 8443 are available (pay attention to your company's firewall problems. If there is a conflict, you need to open the corresponding port for use ).
We also recommend that you use the Subversion Authentication mode. (If it is in the domain, Domain Verification is included, which is relatively secure)
Documentation of the visualsvn Server
1. Operation Interface
On the operation management interface, you can easily create a source code repository or view an existing source code repository. It also allows you to set the permission to use these source code repositories.
2. source code repository Management
You can manage the source code repository by right-clicking the repositories node in the menu tree.
When a new source code repository is created, the visual SVN server can automatically create the default repository directory structure (trunk, branches, and tags subdirectories)
3. Operation permission management
You can right-click the root points of the visualsvn server and select the properties item for the preferred permission Verification Mode. The Subversion Authentication mode is used by default.
To set subversion verification, you must first create a user account. Right-click the users node and select a command.
You need to enter the user name and password to create a user account. Note that the user name and password are case sensitive.
The following is a window that appears after selecting the source code repository attribute items, from which you can add or delete users or groups.
The configuration of the visualsvn server is relatively simple, and other items are not described in detail. Later, we need to work with toisesvn and other client tools.