I. Basic usage of toisesvn

Check out the source code to the local machine and create the folder startkit on the local machine. Right-click checkout. the following form is displayed: totoisesvn basic usage. Step 2: in URL of repository: enter the address of the svn server code library in the text box. By default, click OK to check out the source code. Note: The checkout depth option in contains four options, namely, migrating out all, checking out only the sub-directories and files at the next level, checking out only files, and only checking out empty projects. The default option is the first item. In the above example, we can also access the code library using the web method, and enter idea in the browser. Done! The source code has been successfully checked out to the newly created startkit directory. Open the startkit directory and you can see the folder structure as shown in figure: totoisesvn basic usage method 3. Once you make any changes to the file or folder, the display image of the file or folder will change. I modified two of these files: totoisesvn basic usage method 4. Let's take a look at the pictures corresponding to different States: totoisesvn basic usage 5 we already know how to check the source code into the svn server, how to check out the code from the server to the local machine, and also a simple understanding of the pattern corresponding to different States. Totoisesvn basic usage method 6 check in (import) 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 code library of SVN server. First, right-click the startkit folder. At this time, the right-click menu is shown in: 7. Click Import. the following form is displayed, the http://zt.net.henu.edu.cn is the server name, SVN is the root directory of the code repository, and startkit is a code repository we added in the previous tutorial. Note: the checkbox in the lower-left corner is useless when the source code is checked in for the first time. However, it is very useful when you submit code later. Totoisesvn basic usage method 8 bytes. At this time, the team members can move the source code from the svn server to their machines. Note! Do not import data to the desktop. All the items on the desktop will be imported. 11. Submit the modified files to the svn server. In Figure 2-2-7, I modified the two files in the model file imageinfo. CS and newsinfo. CS, the following shows how to submit to the svn server. Note: When submitting the source code to the server, make sure that the local code is the latest version. Otherwise, the submission may fail or cause version conflict. Right-click the model folder or right-click the blank area under the model file, and click SVN commit... The following form is displayed: basic usage of toisesvn 12. Click OK to bring up the form, as shown in: totoisesvn basic usage method 13 Add a new file to the svn server. We will add a new class file userinfo under the model file. CS, right-click the blank area under the model file, and click SVN commit ..., This is the same as submitting modified files to the svn server. You can also go to the file userinfo. on CS, right-click and choose tortoisesvn => Add. the following form is displayed: totoisesvn's basic usage method 14. Select userinfo. CS file, click the OK button, so that the file is not submitted to the svn server, but the file is marked as a file in the source code library, and its status is changed. After that, we need to submit the svn commit file to the 15 code library on the svn server. The above is about adding files. In fact, the steps for adding folders are the same. 16 updating the Code of the local machine is consistent with the latest version on the svn server. This is also very simple. You just need to right-click the folder to be updated or right-click the blank space under the file, and click SVN update, you can. Note: The update operation may fail due to version conflict. You can use merge [merge] or another method to solve the problem. Alternatively, the update operation may fail because the get lock is locked, this is to unlock the [release lock] first ]. To rename a file or folder and submit the modification to the svn server, right-click the file or folder to be renamed and click tortisesvn => rename ..., Enter a new name in the pop-up form and click OK. This method does not directly rename the file or folder, but marks the name of the file or folder as the name after renaming. We also need to submit it to the svn server using SVN commit to rename it. To delete a file or folder and submit the modification to the svn server, you can directly delete the file or folder, and then use SVN commit to submit the update to the svn server. Another method is to right-click the file or folder you want to delete> tortoisesvn => Delete to delete it. This method is not directly deleted, the state of the file or folder is set to delete. We also need to use SVN commit to submit it to the svn server before deleting it. Note: In fact, from the time you migrate the source code to the svn server, data and files of each version can be moved out at any time even if you have deleted them. Note that this delect is the configuration item on the server. Right-click to delete the local file and it will not affect the server, but you have deleted it from the computer. 17. Change the svn server address: the SVN server address is changed frequently. To avoid re-checkout, you only need to change the server address: the basic usage of totoisesvn 18 precautions:. before modification, we recommend that you perform the update operation before the MOD commit operation, saving the overwrite operation before the mod operation. B. Determine whether the local data is used before the RMV operation, we still do need to delete service-side data. Deleting and submitting commit is the official deletion of server-side data. These are just the simplest functions of tortoisesvn. In fact, they have far more than these functions, you can use other functions in the following tutorial. In addition, the svn server and client networking are described as follows: the B/S structure can be considered, but the B structure can only be viewed and cannot be modified. 1. The client can perform operations such as checkin, checkout, and delect, configuration items are generally completed on the client. 2. The server can only plan the approximate structure of the configuration library, and cannot open or edit the configuration items, in addition, the corresponding configuration file cannot be directly found on the server machine, which is encrypted for security reasons. Therefore, all operations are completed on the client. End Notes: when submitting source code to the svn server, do not submit folders such as bin and OBJ; otherwise, it will be very troublesome. Except for the bin directory of the web project, the DLL generated by referencing other projects in the bin directory of the web project does not need to be submitted. A good habit: if the project references other third-party assemblies, such as enterpriselibrary and FCKeditor, do not reference them from their installation location, but in your solution, add a library directory, copy the required assembly to this directory, and then reference it from the library directory. What are the advantages of this? Think about it for yourself! Experience content is for reference only

　　

I. Basic usage of toisesvn