SVN server-side client configuration and comparison of VSS benefits

SVN version server with full process details (including service side, client)

SVN server-side and client-complete software

SVN vs. VSS Benefits

Difference between the two: http://www.cnblogs.com/zxjyuan/archive/2011/12/07/2280042.html

Source control tools are a very frequent tool for developers to use, only better and faster to improve efficiency, and should not be limited to check-in checkout only.

1, whether to allow simultaneous modification of a file.

VSS: Not available. The first person is locked when modified.

SVN: Yes.

When two people (multiplayer) develop the same module at the same time, it is very common to change to the same file. But VSS can not develop the same file in parallel, in which case the other person can only wait, or have to write the code to other files and other people have done to transfer over, time-consuming and laborious.

SVN can be developed in parallel, merging check-in. In case of special circumstances (where someone needs a lot of modification and others rarely change), you can also perform a lock-and-check out to prevent parallel development.

2, whether to provide a comparison function.

VSS: Provided, but relatively weak, error-prone and unfriendly, and in many cases cannot be compared properly.

SVN: Available, powerful.

When you are done modifying to check in, it is best to check which code has been modified before checking in, which avoids checking in the wrong code (or the Code in the test section).

After the code has been checked in, if you find that the modified code features an exception, you also need to check the differences between the two historical codes.

So the code comparison function is very necessary.

3, fallback to the historical version.

VSS: Not available. You can only manually extract the code and overwrite it.

SVN: Yes. Easy to do with Revert features.

SVN is handy when the code is checked in, but there's a problem.

4, the use of client software.

VSS: VSS software must be turned on to manage.

SVN: Just give a URL (for example: Https://xxx/svn/demo) a folder, right-click Get code. Already get the folder, modify the file, you can go directly to the folder in which to operate. The comparison between the normal file and the modified file is obvious.

5. After modifying more files in vs.

VSS: Management is cumbersome if not in the same folder. Like right: Check out files in multiple different folders, very easy to forget checkin.

SVN: If

Lists all modified files under VS, and provides the ability to right-click to view changes (show changes), version comparisons, and check-in.

6. Open source

VSS: No. Microsoft products are generally used, non-Microsoft product use inconvenience.

SVN: Yes. Wide range of applications, whether Microsoft products or not.

In the case of. NET code and Java code, using SVN facilitates unified management.

7. Support Command line

VSS: No

SVN: Yes.

Support for command lines can simplify many operations. For example, with VSS, every developer will have to turn on VSS software and mouse operations every morning when they arrive at the company.

Use SVN to write the Tortoiseproc command line and save it as a bat batch file. To get the code, double-click the written batch file.

SVN server-side client configuration and comparison of VSS benefits