SVN installation configuration and use (Perfect edition)

1, the selected server installation package:Visualsvn-server-2.1.3.msi,

2. Client Installation package:Tortoisesvn-1.6.2.16344-win32-svn-1.6.2.msi

First, the installation of the server:

Note: Location: For the installation file location, repositories: The position of the managed code warehouse, if the checkbox in front of the use secure connection is selected, the secure connection "https", where the port is 433/8433 available , if the checkbox is unchecked, the default port is 80/81/8080, and the authentication option is subversion.

Win7 64bit Installation visualsvn error occurred:

Servic ' VisualSVN Server ' failed to start. Please check the VISUALSVN server log in Event Viewer for more details Service ' VISUALSVN server ' failed to start.

Workaround:

Control Panel--management tool--service--VISUALSVN server--right mouse button--Properties--Login--Select "Local System Account", click Retry, OK. The installation was successful. (You can't see the admin tool, please change the view)

Category: Project management

Second, the client installation

Click Finish to install.

Third, the service side configuration and use

Add a code base:

Enter the name of the code base in the text box

The above check box is not selected to create an empty code base, and if selected, three subdirectories are created

After you create the code base, the contents are empty, and a few minutes will show you how to move into the source code

Let's start with the security settings and select the Create User on the users on the left

Then add the created user to the project you just created, select the project you just created, right-click Properties ...

Click Add ...

Select the created users, click OK

Permissions to select User rights, there are four choices

1. Inherit from parent inherits from parents

2. No access is not allowed

3. Read Only access

4, Read/write can be read and writable

Click OK

Iv. Basic use of the client

1. Check in source code to SVN server

Suppose we use Visual Studio to create a project in a folder setup, and we want to check the source code of this project into a codebase on the SVN server, right-click the Setup folder and the context menu as follows:

Click Import ...

Where http://192.168.0.101/ is the IP address of the server, SVN is the root of the Code warehouse, project is the code base that we added, the checkbox in the lower right corner is not used for the first time, and you can choose to ignore the files when you check in later , click OK. The following form pops up asking for credentials

If you select the Save outhentication check box, you can save the input credentials.

Enter the user name and password above and click OK.

As above, the source code has been checked into the SVN server, let's look at the SVN server on the existence of check-in source code

3, check out the source code to the machine

Create a folder on this computer setup, right click on svn Checkout ... Pop up the form below

In the URL of Repository: text box below Enter the address of the code base in SVN server, other default, click OK button, start to check out the source code

Description: In checkout Depth, there are four options, namely check out all, check out only the next level of subdirectories and files, check out only the files, check out only empty items, the default is the first.

To open the Setup directory, you can see the following folder structure:

Once you have made any changes to the file or folder, the displayed picture of the file or folder changes. Two files are modified below:

Files that are modified under the Esupermap.lic and Config folders

Below is a look at the corresponding pictures in different states

4. Submit the modified file to the SVN server

I modified the folder under Electric_inspection, right click electric_inspection Select SVN Commit ...

Click OK to pop up the following dialog box

5. Add new files to SVN server

We add Esupermap.lic in Electric_inspection, right click on the blank in the Electric_inspection file, click on SVN commit ..., and the file that was submitted to the SVN server. Alternatively, you can right-click on the file esupermap.lic and click TortoiseSVN, so that the file is not submitted to the SVN server, just mark the file as a file in the source code library and set its state to the modified state. After that, we'll have to commit the file again, so that it can actually be submitted to the code base on the SVN server. Similar to adding folders.

6. Update native code consistent with the latest version on SVN server

Just right-click on the folder that needs to be updated or right-click on the blank in the file and click SVN update.

Note: The update operation may fail because of a version conflict, you can use merge "merge" or other workarounds, or you may fail to lock "Get lock", which requires unlocking "release lock" first.

7. Rename the file or folder and submit the changes to the SVN server

Just right-click on the file or folder you want to rename, click Tortisesvn=>>rename ...,

Enter a new name in the pop-up form. This method is not directly renamed, but instead marks the name of the file or folder renamed, and we use SVN commit to commit to the SVN server.

8. Delete files or folders and submit the changes to the SVN server

The simplest is to delete the file or folder directly, and then use SVN commit to commit the update to the SVN server. Another way is to click on the file or folder you want to delete the right button Tortoise=>>delete Delete, this method is not directly deleted, but the status of the file or folder is set to delete, we also need to use SVN commit to the SVN server before the actual deletion.

Description: In fact, from the time you check the source code into the SVN server, each version of the data and files that you have deleted, you can always check out.

Note: When submitting the source code to the SVN server, be sure not to submit folders such as Bin,obj, otherwise it will be cumbersome, except for the bin directory of the Web project, but the DLL generated by referencing other projects in the Bin directory of the Web project does not need to be committed.

Second: If the project references other third-party control's assemblies, it is best not to simply refer to them from their installation location, but to add a library directory under your solution, copy the required assemblies here, and then reference them from the library directory.

SVN installation configuration and use (Perfect edition)