If our development project needs to be carried out in group mode, coordination and regulatory workflows are very important. If you want to do things, you must first sharpen your equipment, if you can use the version control tool, you will inevitably reach the effect of half the power. I recently learned to find the version control tool on 9CBS, but I found that this post has little post. Leaders who may develop groups are experts in a technical field, and they have more than enough tools. It is often because of the lack of demand to make energy in the implementation details of technology., Anyway, I still want to introduce my experience, I hope I can play a throwing jade. Because the project is developed using BCB, the tool used is a Borland's TeamSource. Although some colleagues are not very impressed with TeamSource, they think that the gap between the VSS is large, but for a 5, 6-person group, It can meet most of the requirements, ok, the words retired. The following is the text :). Use TeamSource to first divide a few concepts: a (main development machine), B (third-party backup machine), C (auxiliary development machine). Here, A, B refers to the development of a local area to a destination computer, and A refers to a computer that establishes a TeamSource project file; group development needs to share the program in some way, B is a computer that developers can access, share The program is implemented on B. Note: The shared folder on b is provided to the team member must be fully accessible. Note: TeamSource must work in a domain environment (if the server's operating system is Win2000, you need to configure Active Directory) Generally a Teamleader in the group development, first of all, a new project should be established by TeamLeader, but in establishing an engineering Previously, a "local directory" must have a "local directory" to save the program source file (generally the code framework), and "Remote Directory" is temporarily uncoded (established in engineering "(ie, a third-party backup machine) The program file can then be uploaded from Local Directory to "Remote Directory" through TeamSource. Local Directory and Remote Directory are called the name in TeamSource. When TeamLeader establishes an engineering, you can add a user, the method is to select the User page in Project | Options, because the initial permissions in TeamSource are read-only, so the add user and other buttons may be disabled, this should be Local View at this time (Local view in TeamSource, by selecting the Local icon) All files, the permissions turn to Write / read, you will find the button enable, you can add users (of course you have access to users!:::: ))). There are also usernames that you want to add when adding users, as you already exist in the domain, as you only log in to TeamSource as domain users as domain users will identify the user identity.
As for the detailed method of setting up the user's permissions, all features are provided on the USER page, as long as you look at it, you will understand! After adding the user, you can back up the code file in Local Directory to a third-party backup machine (that is, the upload just mentioned), lock all files (select all files, press F4), then select all files, points The Do IT button, or select Check I in the Right-click menu. In the dialog of the application, there is a comment text box, you can make other users can see, then other users can know the purpose of your application lock. If the project is established, several folders will be created automatically on a third-party backup machine, and the project file is in the extension of CPJ, which is generally saved in the Archives directory. Now, it is assumed that users DIPPA log in and running TeamSource on a auxiliary development machine. It should first create a new project, but the way to establish import a existing project, which can be built into the project file (.cpj) import on a third-party backup machine, of course There must be corresponding Local Directory on the auxiliary development machine (this Local Directory is responsible for saving a copy of the code file on the backup machine to provide the modification or addition of the user on the source code on the source code. If the import is successful, then the code file can now be backed up The machine is copied to the development machine, the method is to select Project | Pull To ... Generally, the main use is the local view. His display interface is divided into three panels, and the panel on the left displays the files that are changed by other users on the third-party backup. You should Copy to Local Directory; the panel on the right shows you in development The changed file on the machine, and it is recommended that you will change the Check IN to the backup machine; the lower side of the panel is LOCK LIST, which shows that each user is locked. Since I just just contacted TeamSource, there may be a mistake in the article, please look at the official criticism. As for other details of TeamSource, you can try to figure out or refer to the help documentation in use. Author: Orivan on July 26, 2001
