Configuring VSS
Source Code Control Services
Configuration steps:
1, the installation source code control provider.
2, create a source control database.
3, configure the source control server.
4. Set options for each source code control client computer.
Getting Started
Before you can take advantage of the integrated source control features in the IDE and complete the walkthrough, you must first complete the following tasks:
Install a valid source control provider, such as Visual SourceSafe (VSS), in two computers (one server and one client). A source control client is a computer on a network that accesses a shared item in the source control database and stores a copy of the items in a local working folder. The source control server is also a computer in the network that provides shared items to clients from the source control database.
In this walkthrough and later in the walkthrough, we will refer to these computers as SCSrv_Client1 and SCClient2. Both computers are source code control clients. However, SCSrv_Client1 will also host the source control server.
Create a source control database in a shared network folder.
Although source control services are integrated in the visual Studio. NET IDE, you must first install a provider that conforms to the Microsoft source Controls interface (MSSCCI) before you can use these services. After a valid provider has been installed and restarted, you can begin placing solutions, projects, and files under source control. The provider creates a registry key during installation, and each time the IDE is opened, the registry key lets Visual Studio know the provider's presence and its location.
Warning
It is recommended that you do not use visual Studio. NET and separate source control providers to manage the same project or solution. Doing so may result in the inability to access the solution and project from source control.
Visual SourceSafe (VSS) 6.0c is a source control provider that conforms to MSSCCI and is available with the visual Studio. NET Enterprise Development Edition. It is assumed that you have VSS installed in this walkthrough and later in this walkthrough. To integrate source control services with Visual Studio, you must have VSS or an alternate provider installed on each source control client.
Install the visual SourceSafe 6.0c as the MSSCCI provider to run Setup.exe from the root directory of the visual SourceSafe 6.0c version of the installation CD.
After you install the source control provider, the next step is to create a source control database to store the server version of your team's shared files.
Create a source control database The following procedure assumes that you are an administrator, setting visual SourceSafe to the MSSCCI provider on your network, and you want at least one client to have access to this provider. If you are using a different source control program, see the documentation for the provider.
Create a shared network folder for the source control database
In the source control server (SCSRV_CLIENT1), open Windows Explorer and create a new folder named Tracker.
Right-click Tracker, and then select Properties.
In the Tracker Properties dialog box, click the Sharing tab, and then click Share this folder.
You can now create a source control database in a shared tracker. Complete the following procedure in the source control server (SCSRV_CLIENT1).
Creating a Source control database
Click the Start button, point to Programs, point to Microsoft Visual SourceSafe, and then click Visual SourceSafe 6.0 Admin.
In the Visual SourceSafe Administrator dialog box, in the Tools menu, click Create Database.
In the Create new VSS Database in box, type the Universal Naming convention (UNC) path for the network share (for example,
Scsrv_client1/tracker, where SCSrv_Client1 is the name of the computer, Tracker is the name of the new database and network share.
The source control database for Visual Studio. NET has been successfully set up.
The next step is to configure the source control server and client.
Configuring the Source control server
The topics in this section require two computers.
SCSrv_Client1 is the source control server and client. SCClient2 is the source control client.
The server settings are configured in the source control provider's Administrator program. In Visual SourceSafe, use the Options dialog box in the Visual SourceSafe Administrator window.
You can set up a shared checkout so that two or more users can check out and edit the same file at the same time. Change only one server setting, checkout mode. By default, Visual SourceSafe is configured to check out exclusively, that is, only one user can edit a server version of a file at a time. However, if it is a team development environment (for example, the environments that these walkthroughs simulate), it is recommended that you use a shared-checkout pattern.
From the Source control server folder, set up to check out in shared mode. On the SCSRV_CLIENT1 computer, click the Start button, point to Programs, point to Microsoft Visual SourceSafe, and then click Visual SourceSafe 6.0 Admin.
Click Users, click Open SourceSafe Database, and then click Browse.
In the Find Database dialog box, open the folder where you created the tracker database, select the Srcsafe.ini file, and then click Open.
Tracker is added to the list of databases in the Open SourceSafe Database dialog box.
In the Open SourceSafe Database dialog box, select Tracker, and then click Open.
In the Visual SourceSafe Administrator dialog box, on the Tools menu, click Options.
On the General tab, select Allow Multiple checkouts, and click OK.
Now, when you are using a source-controlled item in the tracker database, you can perform a shared checkout. If you have multiple source control databases, you must set this option for each database. For more information, see Walkthrough: Checking out Source-controlled items in a shared way.
Set source control client options for each client computer that is connected to a group's source control server, a unified setting should be established. The client settings are made in the visual Studio. NET Options dialog box, or from a client installation of the source control provider. For users of Visual SourceSafe, you can access all the settings you need to complete this walkthrough from the IDE. The source control walkthrough assumes that you have configured two computers (in this walkthrough, SCSrv_Client1 is both a server and a client) with the following settings:
Visual SourceSafe
An optional configuration file that automatically sets the most appropriate source control options for you and your team's work style. For more information about changing the configuration file, see Setting Source control options.
File sharing
Web Access Methods
If your team is developing a Web application, the first source control setting you should consider is the Web access method. For Visual Studio. NET development, it is recommended that you use the file Share access method (which is also the default setting). With this method, each developer in the team uses the source control project to store the local copy, checking in and checking out changes to the server version of the source-controlled file (sometimes called the master copy).
The FrontPage Server Extensions access method is an alternative method that is more difficult to use. This approach is not recommended for a multiuser development environment. For more information, see Adding FrontPage Web Applications in Shangyuan code management. For more information about both methods, see Web access methods.
to specify Web access methods for client computers
On the visual Studio. NET IDE's Tools menu, click Options, select the Projects folder, and then click Web Settings.
Under Preferred Access methods, select File Sharing.
