Use Google code + SVN for multiplayer Development

From: http://blog.csdn.net/cc_net/archive/2009/08/16/4452890.aspx

When it comes to source code management, CVS, VSS, SVN, and TFs, most people may use them in the company. However, in the company environment, it is basically used in the LAN or by connecting a leased line to a remote server. At ordinary times, when I write some code at home with my friends, I suffer from no code management tools or network environment, but it is very troublesome to pass the code. However, Google Code provides a free SVN space, mainly registering Gmail, and then using SVN for source code management and development with others.

I have introduced it on the Internet, but I have not read it in detail. I have explored it myself and wrote it down to share it with you.

1. access Google Code
Google Code address is http://code.google.com/, if the use of CN to access seems to be unable to access, I here is a blank. Management projects can be accessed directly using http://code.google.com/hosting/ addresses. Use Gmail to log in. [Create a new project] is in the middle of the page. Click it to create a project.

 

2. Create your own project
On the Create Project page, enter the project name, overview, and description. The project name must start with a lower-case name and cannot contain spaces or other symbols. Then I chose the version management system, certificate, and so on. I don't know about this. I just want to select it. Anyway, this has been selected and [Create project] is available. Note that the project name may conflict. If the project is successfully created, you can go to the Project Management page.

 

3. Project Management
In project management, the "project home" menu on the top shows the overview and description of the project. Click source to manage the source code. There are two addresses, one starting with HTTPS, the other starting with HTTP, And the other starting with HTTPS with encryption. Therefore, if you want to commit new code, you need to use this address. If you just get the code, you can only use the address starting with HTTP.

When using the HTTPS address, you need to provide the user name and password. Here, the user name is The Gmail user name, while the password is generated by Google for each project, rather than the Gmail password. Click the blue link next to [when prompted, enter your generated googlecode.com Password] to view the password. This password is the password for all your projects, not for each project.

 
4. User Management
After the project is established, you can add others to the project so that you can develop them together. Click administer at the top, click project members, and enter the user Gmail you want to add below. There are project owners, project committers, and project contributors. The details are displayed on the right. Click Save. After logging on to other users, you can view the projects you have joined in the upper-right corner of my favorite. Find the password as described in section 3.

Other management
Google Code also provides Wiki and other functions, so I don't know much about it.

6. Install the client and vs plug-in
After completing the above work, upload the source code and documents. However, I have been looking for a long time and do not know how to upload it. I thought it was a direct webpage upload, and I had to install the svn client. Here

Http://tortoisesvn.net/downloads can be downloaded to the latest tortoisesvn, which should be the most commonly used SVN client software. Poor E users also provide Chinese language packs.

After installing the client, restart your computer and connect to the svn server remotely. In the URL, enter the https url provided by Google, and then enter the username (Gmail) and password (Project password). After saving, it will be OK. The client can connect to multiple URLs. You can select the one to connect to at each startup.

 

 

Support SVN vs plug-in I am using ankhsvn, http://ankhsvn.open.collab.net/servlets/ProjectDocumentList? Folderid = 198 you can download to the latest version. Currently, vs2010 is supported. Earlier versions have poor support for vs2008, the file status is incorrect, and cannot be submitted. It is enough to switch to the latest version. It takes a long time to configure vs during installation. Do not think it is dead.

If you only install ankhsvn and do not install tortoisesvn, you can also find in vs that the operation functions are much less, such as branch and merge.

 

7. Use vs for development and source code management
Go to Vs and choose tools> Options> source control. ankhsvn is configured by default. Click File> subvwrsion to open the source code on the server. Like other tools, you need to select a local path for saving.

 

1: File status

Blue check: Check out status; orange check: File Modified status; orange check box: File Modified and saved; plus sign: New file added.

2: SNV Version Control

Unlike VSS, VSS is locked by default and requires manual check out, while SVN is automatic check out. Isn't there a conflict? In fact, this is the same as what VSS allows multiple people to pull. When you commit, you will check the version, and automatically merge or prompt for conflicts or version expiration.

 

Get the latest code: Get the latest code from the server, but if you modify the file and pull the latest code, at this time, the system will automatically merge the modified parts with the latest code. If there is a conflict, the system will prompt you to modify the conflict.

Get the code of the specified version: You can view the code of the specified version by viewing the history or specifying the version number. This will also merge the code. Note that the version number of SVN is different from that of VSS. It is a global version number, rather than a version number for each file. Pay special attention to this because you may find that the version number of a file may be skipped.

Switch: You can switch the current version to a specific version. Different from getting a specified version, switch automatically merges different parts.

Revert: restore to the status before modification. Note that if you modify the file, obtain the latest code, and restore the file, the latest version is restored, instead of the previous version. Note that

Version conflict: There are two types of version conflicts,

If your current version is 1 and the server version is 2, you can modify or submit it. The server will prompt that your local version has expired. You can pull the latest code and submit it again after resolving the conflict;

If your current version is 2 and the server version is 2, and you get the code of version 1 from the server, modify the code, and submit the code, this will not prompt that the version has expired, it overwrites version 2 on the server and becomes version 3. This will throw the code.

Lock: SVN provides the lock function, which is the same as the single-user check-out of VSS and cannot be modified at the same time. However, Google SVN currently does not provide the lock function, so there is no way to use it.

Eight SVN documents
I have never used SVN source code management before, so I feel different in some places. For details about SVN version control methods and SVN introduction, refer to the website

Http://www.subversion.org.cn/svnbook/1.4/svn.basic.vsn-models.html

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/cc_net/archive/2009/08/16/4452890.aspx