Installation and Use of Version Control Software sourcegear vault3.5.2

Introduction: Why version control is required? 1. Scenario 1: programmers A and B Modify the same module together. Both of them worked hard for several days and finally saved them back to the server. You can use it to find that one of the changes has been washed away! 2. scenario 2: User 1 finds an error and sends it to programmer A for modification. User A directly changes the version that the user is using after modification. User 2 wants to add a function and hand it over to programmer B for modification, B Also works as a result, resulting in a's changes being overwritten by B and lost. 3. scenario 3: The user proposed to need a new function. programmer A worked hard for a few days. After the change, the user said that the new function was not needed. programmer A found that the original version of the program could not be found, it took another few days to change the program back. Simple Working Principle of version Manager The version manager saves all project source files (including various file types) to the database in a unique manner. Developers cannot directly modify files in the database, instead, the version manager copies the source program or subitem program of the project to the working directory of each member for debugging and modification, then, submit the modified project file as checkin to SGV for comprehensive updates. Users can quickly and effectively share files as needed. Once a file is added to SGV, its changes are recorded. You can restore the earlier version of the file. Other members of the project team can also see the latest version of the file, and modify them. SGV also records new changes. The following describes some source code management tools on the. NET platform. Visual sourcesafe, CVS, PVCs, clearcase, sourcegear sourceoffsite, and sourcegear vault Sourcegear vault (SGV) and visual sourcesafe (VSS) Security (database/file sharing, directory permission) Stability (> 1G) Speed (incremental storage algorithm, Io) Support Remote Access Integration with IDE SGV Solution Install SGV's WebService and SQL database on a server, create a database (repository) for storing the entire project, and then create various folders in the database, the SGV administrator creates an account and their respective permissions for each member of the group; Install the SGV client software on the PC of other members of the development team, and create your own working directory. In this way, during the software development process, they only need to log on to the SGV server by integrating ide or client software, and checkout is currently working on the project or file, if any modification is made, submit the check in to the SGV server for unified update at the end of the work. How do I deal with projects managed by VSS? Method 1 "File"-"Source code management"-"open from source code management"-log on to SGV-select working directory-select project Method 2 1. "work in disconnected mode" to open a local project 2. "file"-"Source code management"-"Change source code management" Basic operations for integrated ide Add solution and project to source code management Open or add a project from source code management Change source code management Check out Cancel checkout Check in View status (sourcegear vault attribute) Get the latest version View history Basic operations on common clients Change Password (tools-chage password) Log out (file-disconnet from server) Project selection (file-choose repository) Create a folder Add folders/Files Automatically detect new files Search for files Delete/restore a file View/modify files Create a working directory Check out a folder/File) Cancel checkout Check in) Share) Split a file (Branch) Rename folders/Files Move folders/Files Show history) Get earlier versions Create a label for a file or project) Do not modify folders/Files (PIN) Folder/file ignore (cloak) Well, after posting so many things, you should basically know the importance and principles of version control. There are also a lot of basic client operations and skills that you can study and understand in use, the following figure demonstrates the installation and use process: Install sourcegear vault3.5.2 (available on the official website http://www.sourcegear.com/vault/downloads.html) Generally, you do not select a client for Server Installation (unless the server and client are installed on a single machine at the same time), as shown in. Select the IIS process mode. We use the default network service (you can also choose Custom M. However, to use a dedicated Windows account, you can configure it as needed) Set the administrator password (the default Administrator account is admin), for example: Enter the authentication information for connecting to SQL. Next we select the SQL Server Authentication mode. log on to the server named SA (this user must have the permission to create a database in SQL) The following figure shows how to set up the data information and select the encoding mode. Here I didn't set the encoding mode. Click OK. After the installation is complete, vaultserver creates two virtual directories in IIS: vaultservice and vaultshadowfolder. You can download these directories through web (read-only) to view recent changes and versions. Vault is recommended for many reasons because it is based on SQL Server because it is used. net, because it uses XML Web Services as the communication protocol. Don't forget it. sourcegear Vault provides free trial authorization for 10 users a month. If you are not afraid of trouble, you can also update the license every month. Of course, if you are a personal user and only manage some of your own code, you don't have to worry about it, after the free trial authorization expires, you can continue to use the admin account, which is unlimited. Get serial number: https://store.sourcegear.com/sgstore/vaultdemo.aspx Let's take a look at the login interface of the Admin Tool on the server: After logging in with the admin account, you can configure permissions for other users, such as permission allocation and management. I will not talk about it here. Let's take a look at it. The above is the installation process on the server. The client has no installation skills. During the installation process, remember to check "make vault you default SCC provider" and click OK. Now you can use. the following describes how to check in vaultserver for a project created by net2005: Call the following figure in the options of vs. net2005 tool. You can see the source code management plug-in after installing sourcegear vault (by default, you do not need to modify it unless you install multiple source code management software) Next let's take a look at how to add the solution to sourcegear vault3.5.2 and right-click the solution, as shown in: In the displayed window, enter the user name and server name or IP address (the first time you create an account, you must use an account with permissions) We have created a folder named "album management" for this project" If you can also create multiple folders in the "album management" folder, such as "development documentation" and "source code", you can put the development documentation and source code in these two folders respectively, you can see that I have added numbers 1 and 2 in front of these two folders. This is a technical problem. We can sort these two folders in order. After creating the directory, select "2 source code" and check the project in this folder. There are also some tips for use. For example, you can set whether to automatically prompt for check-out in the source code modification. If you set "prompt for check-out ", when you modify the code, the system will automatically prompt you to check out the file and comment. You can record the reason for your check-out in the comment, with this article, you can easily manage your own code. Let's take a look at the following benefits of vaultserver.3.5.2: 1. The server is based on Web Services and thus does not need to be accessed through file sharing (with write permission) Like VSS) 2. Management of users and user groups (just like VSS, there are only a few basic types of permissions, which are far inferior to starteam, but CVS is quite adequate) 3. Similar to the comparison of VSS versions, history records, merge, branch/branch merge, and other functions, it is no difference at all. 4. Key data is stored in the database (sqlserver) and backed up on the server 5. WebClient is provided. Currently, only the file content can be viewed and viewed on the web. 6. Divide the repository knowledge base to facilitate management and use. 7. Supports SSL (secure socketlayer) protocol connections, in this way, you do not have to worry too much about the security issues caused by HTTP/WebService-but I have not been able to set access over the Internet, and access can be successful using VSS, however, the access speed is too slow, so I gave up. Now we use sourcegear vault3.5.2 + VPN for Internet access, which is much safer than HTTP/WebService and faster than VSS (estimated time, I didn't really calculate the time, but I just estimated it ). With it, the biggest advantage is that after returning home, we can still maintain connections with the company's servers, without disconnecting solution-we had to carefully compare/merge when we went to work the next day, and checkin. Regardless of the file type (text file, image file, binary file, sound file or video file), you can save the file to the database to help you manage the project. You can quickly and effectively share files between two or more projects. When you add files to the vault, the files are backed up to the database so that users in the same group can access the files, any changes to the file will be saved to the vault so that you can restore the historical version of the file at any time. The user team members can get the latest version of any file, modify the file, and store the new version of the file in the database.