1. Why use VisualSVN Server instead of Subversion?
Reply:
Because if you use Subversion directly, then on the Windows system, if you want it to start with the system, you need to encapsulate SVN Server as a windws service, and you need to control user permissions by modifying the configuration file. VisualSVN Serve integrates with Subversion and Apache, eliminating all of the hassle. When installed, SVN Server is already packaged as a windws service, and the configuration of Apache Server is only on the graphical interface, specifying the authentication method, access port, and other simple operations. In addition, the management of user permissions is also configured through the graphical interface.
2. Why not use TFS?
Reply:
Since we started with Subversion and TortioseSVN, we didn't change other software. As for TFS, I haven't used it so far, in fact, I just read some articles and don't know much about it.
3. Is VisualSVN Server free?
Reply:
Yes, VisualSVN Server is free, while VisualSVN is chargeable. VisualSVN is the client of SVN, integrated with Visual Studio, VisualSvn Server is the server side of SVN, including Subversion, Apache and user and permission management, the advantages have been mentioned above.
Alright, back to business, officially starting our tutorial today.
1. VisualSVN Server configuration and usage method [server-side]
After installing VisualSVN Server [see here for the installation process], run VisualSVN Server Manger, the following is the boot interface:
Okay, let's add a codebase [Repository], as shown below:
Create a new codebase as shown in the image above, enter the codebase name in the text box shown in the image below:
Note: If the CheckBox in the above figure is selected, three subdirectories will be created under the codebase StartKit: trunk, branches, and tags; If unchecked, only an empty codebase StartKit is created.
Click the OK button and the codebase is successfully created.
Once you've created your codebase, there's nothing in it. I'll explain how to migrate into the source code in the second part of this tutorial.
Next, we start the security settings, right-click on Users on the left:
Enter the above information, click OK, and we will create a user. Follow the above process to add users Developer1, tester1, and manager1 respectively, and now we start adding these users to the project we just created:
Click "Add..." button, select the user we just added in the figure below, click the OK button:
Note: You may have noticed the Groups in the figure below, yes, you can also create groups first, add users to each group, and then authorize the groups.
Authorize users or groups as shown in the following figure:
By clicking the "OK" button, the user above has different permissions to access the StartKit codebase.
Because the user starter is a newcomer to the team and does not want him to submit new code to the codebase, he can only read the code in the codebase, not submit the code. tester1 is a tester and is not responsible for code writing, so it is also read-only. Developer1 and manager1 are developers and project managers, and naturally have read and write permissions.
In the actual project development process, it is often impossible for there to be only one developer and tester, so it is more convenient to use groups to authorize, and you can practice this by yourself.
2. Basic usage of TotoiseSVN
In Project Management Practice Tutorial 1, If you want to do a good job, you must first sharpen your tools [Basic Tools], I have explained how to install TortoiseSVN. In the above explanation, we have already talked about how to use VisualSVN Server, and today I will talk about the simple use of TortoiseSVN.
1. Check in the source code to the SVN server If we use Visual Studio to create a project in the folder StartKit, we need to check the source code of this project into the codebase on the SVN Server, first right-click on the StartKit folder, the right-click menu at this time is as shown in the figure below:
Figure 2-2-1
Click Import, and the following form pops up, where http://zt.net.henu.edu.cn is the server name, svn is the root directory of the code repository, and StartKit is a code base we added in the previous tutorial:
Note: The CheckBox in the bottom left corner is not useful when you first check in the source code, but it is very useful when you submit the code later.
Figure 2-2-2
Click the OK button, and the following form will pop up, asking you to enter your credentials:
Figure 2-2-3
Enter the username and password in the above form, and click the OK button:
Figure 2-2-4
As shown in the figure above, the source code has been successfully checked into the SVN server. At this point, team members can migrate the source code from the SVN server to their own machines.
|
Posted on 3/17/2017 3:31:41 PM
|
|
|
|
Posted on 3/17/2017 3:39:39 PM
|
Landlord|
Posted on 3/17/2017 3:41:06 PM
|
Posted on 3/19/2017 5:04:39 AM