Server side: 1. Server-side installation of IIS (not available on internet) 2. Install the server side of the VSS2005 (of course, if the local test, the client also installed) 3. Select Microsoft Visual SourceSafe administration->open SourceSafe database->create a new database->c:/vss2005 ( New directory)->vss2005 (default)->local-modify-unlock-model->ok->open 4. Add a normal User A (domain to add a domain user, otherwise add Local users) 5. In the Explorer, set the shared and secure pages of c:/vss2005 to add shares, so that user A has sufficient privileges on the security page and also adds a sufficient privilege//easy to overlook important step 6. The reversed Microsoft Visual SourceSafe administration-> opens the database->server-config-> hook-and-Choose Enable SourceSafe that you just established Internet for this computer and enable SourceSafe Internet for this database->ok (if not the Internet, this step does not) Client 1. Install vss2005 2. Visual studio2005->option-> Source Control-> Select Microsoft Visual SourceSafe (Internet) 3. Source Control-> Plugin settings-> Advanced-> Cancel always use SSL to connect to the server. Now Setup completes Test 1. Create a new project 2. File-> Source Control-> Add a solution to the source Control->open SourceSafe Database dialog box 3. Add-> Enter the server name or IP address-> Enter the UNC name of the shared directory as [Url=file:////bomexs3/vss2005]//bomexs3/vss2005[/url] 4. In the Pop-up Authentication dialog box, enter the password for the A that you just created (if the Security page is not set in step 4th of the server side, the VSS Web service cannot open the database is prompted). 5. Ok 6. Select the newly established database->open-> warning-> determine->add to SourceSafe databse dialog box-> Use default values->ok After the release of VSS2005, it has long been heard that internet access can be supported, which is an interesting feature. The first two days are free, the installation configured a bit, a successful visit. Now the installation process is released and shared. Step 0: Pre-installation considerations Server side: Because Internet access is implemented through Web service, you must first configure IIS before you install it. Installing VSS2005 seems to automatically install the. NET Framework 2.0, but I installed the. NET Framework 2.0 and enabled ASP.net 2.0 beforehand. Client: Only Visual Studio 2005 supports VSS's Internet access by default, so clients also install VS2005. Step 1: Install VSS2005 Install VSS2005 all the way next is OK. Both the server and the client are to be installed. Step 2: Create the VSS database and enable Internet access This step is the most critical, if the configuration is not a problem, half the success. 1. Start Microsoft Visual SourceSafe Administrator 2, create a VSS database
All the way Next,ok. 3. Enable Internet access
Select Menu Server--〉configure ..., pop-up Server Configuration dialog box For the Enable SourceSafe Internet for this computer and enable SourceSafe Internet for this database to tick, enter the server's IP address. Press OK, my God, No. System prompts to use share path access. Again First go to the resource manager, share the VSS database path, and set the user's shared access rights. Then enter Microsoft Visual SourceSafe Administrator Select Menu file--〉open SourceSafe Database ..., pop-up a dialog box Click Add ... button, press Next, and enter [Url=file:////server/vss]//server/vss[/url] When you need to specify a location. Finally select the newly added library, click Open, and then repeat steps 1 and 2. There will be some hints in the middle, no matter he, answer yes. If you don't get a hint, you have the server side configured.
4. Client access via Internet
Install good VSS2005 Open Visual Studio 2005 Select Menu Tools--〉options--〉source control--〉plug-in Selection Select Microsoft Visual SourceSafe (Internet) Select Menu Toolsàoptionsàsource controlàplug-in settingsàadvanced ... Remove always use SSL to connect to the server front of the hook Open a project randomly, select menu Fileàsource controlàadd project to Source control System Open SourceSafe Database dialog box Click Add ... Button You'll notice that the second step becomes the address and folder you want to enter. Enter the IP address of the server and the shared directory name (for example: [Url=file:////server/vss]//server/vss[/url]) Click Open, the Login dialog box appears, enter your account and password on the server. If you successfully log on, the Add to SourceSafe internet dialog box appears. You can add the project to the Internet. Done. Ha ha. Use of Microsoft Visual SourceSafe 2005 in Vs.net Service-Side Installation 1. Install Microsoft Visual SourceSafe2005 to a single server, install mode select full 2. Run Microsoft Visual SourceSafe Administration 3. Create a new database, remember the directory where the database is located, and set it to be shared, permissions are fully controlled 4. Add New User Client Installation 5. Install Microsoft Visual SourceSafe2005 on the local machine, install mode can choose Default 6. Run Microsoft Visual Source on the local machine and select the database in the shared directory on the server as the local database when the logon screen appears 7. Open Vs.net and choose to open the project file you want to manage 6. From the File menu, select Source Control, and then select Add selected items to source control. 7. Select the name of the SourceSafe project file to be established and determine. 8. After the Web site is added to VSS, the folder name is best changed, the default name is unfriendly, and the original inconsistency. Open controlled code on other machines 1. Install SourceSafe the same as the client 1. Open Vs.net 2. In the [File] menu, choose [Source Control], and then select [Open from source code Manager], select the project file, (at this time the project file default build path for the original established path, if you want to change the right key to the project file selection path) 3. Check out the file to create a local copy will report a window error, even if the Web data is not open, at this time, close the item open again. |