Export (0) Print
Expand All
Expand Minimize

Managing Source Control

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Microsoft's SharePoint Team Services and Microsoft FrontPage 2002 Server Extensions provide built-in source control (on Microsoft Windows or UNIX platforms) and can also work with Microsoft Visual SourceSafe for Windows version 5.0 or later (Microsoft Windows platform only). With either source-control method enabled, authors can use commands in a SharePoint Team Services–compatible Web page editor, such as Microsoft FrontPage 2002, to check pages and other files in and out of a SharePoint team Web site or FrontPage-based Web site. With Visual SourceSafe (VSS) source control enabled, authors benefit from advanced functionality such as tracking and storing changes to each file, reviewing a file's history, and returning to earlier versions of a file.

With either type of source control enabled, SharePoint Team Services and FrontPage 2002 Server Extensions perform background check-outs and check-ins after some operations are performed in a SharePoint Team Services–compatible Web page editor. For example, when a theme is applied to a Web site that has source control enabled, each page that is not in use is checked out in the background, the new theme is applied, and the page is checked in. By doing this, SharePoint Team Services and FrontPage 2002 Server Extensions protect the consistency of a Web site and help prevent it from containing errors such as broken hyperlinks.

The following table describes how SharePoint Team Services and FrontPage 2002 Server Extensions implement source control for common page and Web site operations.

When an author...

SharePoint Team Services or FrontPage 2002 Server Extensions

Unless

Edits and saves a page that has not been checked out

Checks the page out, updates it, and checks it back into the Web site and the VSS project (if VSS control is enabled).

 

Moves a file

Moves the file in the Web site and the VSS project (if VSS control is enabled). Then, checks out every page in the Web site that contains a hyperlink to the moved file, updates all hyperlinks to it, and checks every page back in.

A page with a hyperlink to the moved file is checked out. In this case, the author cannot move the file.

Renames a file

Renames the file in the Web site and the VSS project (if VSS control is enabled). Then, prompts the author to check out every page in the Web site that contains a hyperlink to the moved file, updates all hyperlinks to it, and checks every page back in.

A page with a hyperlink to the renamed file is already checked out. In this case, the author cannot rename the file.

Deletes a file

Deletes the file in the Web site and the VSS project (if VSS control is enabled).

The file is checked out. In this case, the author cannot delete the file.

Imports a file

Checks the file into the Web site and the VSS project (if the file is new, and VSS control is enabled). If the file already exists in the Web site, the file is checked out, updated, and checked back into the Web site and the VSS control project.

 

Creates a new page

Checks the page into the Web site and the VSS project (if VSS control is enabled).

 

Edits and saves a page or graphic that is included in other pages

Tries to check out every page in the Web site that includes the page or graphic, updates all pages, and checks every page back into the Web site and the VSS project (if VSS control is enabled).

A page that includes the page or graphic is already checked out. In this case, the page is not updated. To update all pages, have all authors check in all pages, then use the Recalculate Hyperlinks command (Tools menu in FrontPage).

Applies a theme to a Web site

Tries to check out every page in the Web site that uses the default Web site theme, updates all pages, and checks every page back into the Web site and the VSS project (if VSS control is enabled).

A page that uses the default theme is already checked out. In this case, the theme is not applied to the page. To update all pages, have all authors check in all pages, then reapply the theme to the Web site.

Edits and saves a shared border

Tries to check out every page in the Web site that contains the shared border, updates all pages, and checks every page back into the Web site and the VSS project (if VSS control is enabled).

A page that uses the shared border is already checked out. In this case, the shared border is not updated. To update all pages, have all authors check in all pages, then remove and reapply the shared borders to the Web site using the Shared Borders command (Format menu in FrontPage).

Enabling and configuring Microsoft Visual SourceSafe

Integration with Microsoft Visual SourceSafe 5.0 or later is available on Microsoft Windows Server 2003 (FrontPage 2002 Server Extensions only), Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional, and Windows NT Server 4.0 or later. Install Visual SourceSafe to an NTFS file system–formatted partition.

Enabling SourceSafe integration

To use Visual SourceSafe with a SharePoint team Web site or FrontPage-based Web site, you must choose Enable SourceSafe Integration during Visual SourceSafe Setup.

To enable SourceSafe integration 

  1. Run the Visual SourceSafe installation program, Setup.exe, from the Visual SourceSafe CD.

  2. Select the Custom installation option.

  3. In the Visual SourceSafe Custom dialog box, select the Enable SourceSafe Integration check box.

  4. Click Continue.

Configuring Visual SourceSafe for remote use

You can store your Visual SourceSafe database on the same computer as the Web server (a local database) or on a different computer (a remote database).

Note   Although it is possible to configure the Visual SourceSafe database on a separate computer from the Web server, this is not considered a common scenario and may not work in all circumstances.

If the database is on the same computer as the Web server but is accessed using UNC paths, the database is considered to be remote. For example, the following database is remote because the Srcsafe.ini file on the Internet Information Services computer has one of the following lines:

Data_Path = X:\vssdata
Data_Path = \\IIS-Machine\vssdata 

You can also view the registry to find out whether the database is accessed with UNC or mapped paths.

You should note which configuration you have, because if you are using a remote database, you must to complete a few extra steps below.

About the Visual SourceSafe INI file

SharePoint Team Services or FrontPage 2002 Server Extensions must find a Srcsafe.ini file to perform Visual SourceSafe operations through OLE automation. Visual SourceSafe 5.0 usually uses the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SourceSafe\SCCServerPath. While this key points to the Ssscc.dll in the VSS\Win32 directory, SharePoint Team Services or FrontPage 2002 Server Extensions uses the Srcsafe.ini file in the VSS directory. Visual SourceSafe 6.0 normally uses the Srcsafe.ini file in the Web server's installation of Visual SourceSafe.

Setting Visual SourceSafe directory permissions

Before your users can use Visual SourceSafe, you must set directory permissions on the Visual SourceSafe directory structure and files. Generally, you assign Change (Windows NT 4.0) or Modify (Windows Server 2003 family and Windows 2000) permissions to all Visual SourceSafe logon accounts for all files and subdirectories under the Visual SourceSafe server installation directory (including the Visual SourceSafe data directory if it is in a different location). You should also grant Administrators and System accounts Full Control to the entire Visual SourceSafe directory hierarchy. Although tighter file restrictions are possible, full Visual SourceSafe functionality can be jeopardized by tighter restrictions.

You configure the security and sharing permissions to the Visual SourceSafe directories on the computer that contains the Visual SourceSafe database. When you are assigning permissions, be sure to grant at least read permissions to all Visual SourceSafe logon accounts for the following files:

  • Srcsafe.ini

  • Um.dat

  • Users.txt

Be sure to also grant at least read\write permissions to all Visual SourceSafe logon accounts for the following files or directories:

  • Vss\Users\<logon account directory>\

  • Vss\Data\

  • Vss\Temp\

  • Rights.dat

  • Status.dat

The procedures for assigning permissions are different for Windows Server 2003, Windows 2000, and Windows NT 4.0. Use the procedure for the operating system you are using.

To set Visual SourceSafe directory permissions for Windows Server 2003 family or Windows 2000 

  1. In Windows Explorer, right-click the directory or share, click Properties on the shortcut menu, click the Security tab (Sharing tab for a shared folder).

  2. Select the group name that you want to set permissions for, and then in the Permissions list, next to Modify, click Allow.

To set Visual SourceSafe directory permissions for Windows NT 4.0 

  1. In Windows Explorer, right-click the directory or share, click Properties on the shortcut menu, click the Security tab (Sharing tab for a shared folder), and then click Permissions.

  2. Select the group name that you want to set permissions for, and then in the Type of Access list, select Change.

Setting permissions for a remote Visual SourceSafe database

If you are using a remote Visual SourceSafe database, you must also set the WWW Service properties on the Web server computer. Also, if you are allowing Anonymous access to your server, you must also set Anonymous account permissions for your remote database.

To set the WWW Service properties 

  1. In the Internet Service Manager, open the Internet Information Server folder, right-click the Web server, and then click Properties on the shortcut menu.

  2. In Master Properties, click WWW Service, and then click Edit.

  3. Click the Directory Security tab, and then under Anonymous Access and Authentication Control, click Edit.

  4. For Windows Server 2003 or Windows 2000, select the Basic authentication (password is sent in clear text) check box and clear the Integrated Windows Authentication check box.

    For Windows NT 4.0, select the Basic (Clear Text) check box and clear the Windows NT Challenge/Response check box.

    Because you have turned off Windows NT Challenge/Response authentication (Windows NT 4.0) or Integrated Windows Authentication (Windows Server 2003 or Windows 2000), users must now type their user name and domain password when they open a Web site. Use the format DomainName\UserName for the user name when working with multiple domains.

  5. If you want to allow anonymous access to your server, select the Anonymous access check box (for Windows Server 2003 or Windows 2000) or the Allow Anonymous check box (for Windows NT 4.0).

If you are using an anonymous account, you must also set Anonymous access for the computer with the Visual SourceSafe database. The procedures for setting Anonymous access are different for Windows Server 2003, Windows 2000 and Windows NT 4.0. Use the procedure for the operating system you are using.

To set Anonymous access for Windows NT 4.0 

  1. In User Manager For Domains, on the User menu, click New User to add the Web server's Anonymous account. For example, if the Anonymous account on the Web server is IUSR_WEBSRV, add that user as a local account.

  2. Give the account the same password as it has on the Web server.

  3. Click OK.

  4. Under Username, click the Anonymous account.

  5. On the Policies menu, click User Rights.

  6. From the Right list, click Log on locally.

    Make sure that the Anonymous account is listed in the Grant To box individually or as a member of one of the groups, and then click OK.

To set Anonymous access for Windows Server 2003 or Windows 2000 

  1. In Computer Management, click the plus sign (+) next to Local Users and Groups.

  2. Click Users.

  3. On the Action menu, click New User to add the Web server's Anonymous account.

    For example, if the Anonymous account on the Web server is IUSR_WEBSRV, add that user as a local account.

  4. Give the account the same password as it has on the Web server.

  5. Click Create.

  6. In the list of user names, right-click the Anonymous account, and then click Properties.

  7. Click the Dial-in tab.

  8. Under Remote Access Permission (Dial-in or VPN), select Allow access.

    Note that you can also set remote access by using a remote access policy. For more information, type remote access policies in the index for the Windows Server 2003 family or Windows 2000 Help system.

  9. Click OK.

Configuring user accounts for use in Visual SourceSafe projects

Microsoft Visual SourceSafe includes a Visual SourceSafe Administrator utility that you use to set up and configure accounts for use in VSS projects. For Visual SourceSafe 5.0 and later, the Visual SourceSafe Administrator is available on the Start menu.

To enable Visual SourceSafe integration with SharePoint Team Services or FrontPage 2002 Server Extensions, you must add the following user accounts by using the Visual SourceSafe Administrator.

Users and groups

VSS permissions

All administrator, author, and content manager groups and users for SharePoint Team Services or FrontPage 2002 Server Extensions

read-write

The Internet guest account

read

You can add both individual user and group accounts to Visual SourceSafe.

To add a user or group account in the Visual SourceSafe Administrator 

  1. Open the Visual SourceSafe Administrator.

  2. On the Users menu, click Add User.

  3. In the Add User dialog box, in the User name box, type the user or group name and leave the Password field blank.

  4. Click OK.

After you have added the users and groups, you must configure the accounts to automatically log in.

To configure the Visual SourceSafe accounts 

  1. In the Visual SourceSafe Administrator, add the SharePoint Team Services or FrontPage 2002 Server Extensions users (without passwords).

  2. On the Tools menu, click Options, click the General tab, and make sure that Use network name for automatic user log in is selected.

Configuring the Anonymous account

If you use an Anonymous account, you must configure it on the Web server computer. Before you configure the Anonymous account, check that the Anonymous account has the same password in both Internet Services Manager (Internet Information Services in Windows Server 2003) and Computer Management (Windows Server 2003 or Windows 2000) or User Manager For Domains (Windows NT 4.0). You might have to reenter the password in both places.

To set or change the Anonymous account password in the IIS Service Manager 

  1. In Internet Services Manager or Internet Information Services, open the Internet Information Server folder, right-click the Web server, and then click Properties on the shortcut menu.

  2. In Master Properties, click WWW Service, and then click Edit.

  3. Click the Directory Security tab, and then under Anonymous Access and Authentication Control, click Edit.

  4. Under Allow Anonymous Access, click Edit.

  5. Change the password for the Anonymous account as needed, and then close all remaining dialog boxes.

    Note the name of the Anonymous account, because you will need to identify it in Computer Management (Windows Server 2003 or Windows 2000) or User Manager For Domains (Windows NT 4.0).

  6. Open Control Panel, and then double-click Services.

  7. Click World Wide Web Publishing Service, click Stop, click Yes to confirm, and then click Start.

After you set or change the password in Internet Services Manager, you must also set or change the password in Computer Management (Windows Server 2003 or Windows 2000) or User Manager For Domains (Windows NT 4.0).

Note   Passwords appear as 14 characters, regardless of the actual length of your password.

The procedures for setting and changing passwords are different for Windows Server 2003, Windows 2000 and Windows NT 4.0. Use the procedure for the operating system you are using.

To set or change the Anonymous account password in the Computer Management (Windows Server 2003 or Windows 2000) 

  1. In Computer Management, under Local Users and Groups, click Users.

  2. In the list of users, right-click the Anonymous account, and then click Properties.

  3. Change the password for the Anonymous account as needed, and then click OK.

To set or change the Anonymous account password in the User Manager For Domains (Windows NT 4.0) 

  1. In User Manager For Domains, under Username, click the Anonymous account (if you are uncertain which account this is, see the previous procedure).

  2. On the User menu, click Properties.

  3. Change the password for the Anonymous account as needed, and then click OK.

After the password is set, you can configure the Anonymous account to have logon rights and to log on automatically. The procedures for configuring the logon rights for the Anonymous account are different for Windows Server 2003, Windows 2000 and Windows NT 4.0. Use the procedure for the operating system you are using.

To configure logon rights for the Anonymous account on Windows NT 4.0 

  1. In User Manager For Domains, under Username, click the Anonymous account.

  2. On the Policies menu, click User Rights.

  3. From the Right list, click Log on locally.

    Make sure that the Anonymous account is listed in the Grant To box individually or as a member of one of the groups, and then click OK.

  4. With the Anonymous account still selected, on the User menu, click Properties.

  5. Clear the User Must Change Password at Next Logon and Account Disabled check boxes, and then click OK.

To configure logon rights for the Anonymous account on Windows Server 2003 or Windows 2000 

  1. In Computer Management, under Local Users and Groups, click Users.

  2. In the list of users, right-click the Anonymous account, and then click Properties.

  3. Click the Dial-in tab.

  4. Under Remote Access Permission (Dial-in or VPN), select Allow access.

    Note that you can also set remote access by using a remote access policy. For more information, type remote access policies in the index for the Windows Server 2003 or Windows 2000 Help system.

  5. Click the General tab.

  6. Clear the User must change password at next logon and Account is disabled check boxes, and then click OK.

After you have configured the logon rights for the Anonymous account, you add the Anonymous user to Visual SourceSafe and configure the permissions for the Anonymous account in the same way that you configured the other users.

To add and configure the Anonymous account in the Visual SourceSafe Administrator 

  1. Open the Visual SourceSafe Administrator.

  2. On the Users menu, click Add User.

  3. In the Add User dialog box, in the User name box, type the Anonymous account user name, and leave the Password field blank.

  4. Click OK.

  5. On the Tools menu, click Options, click the General tab, and make sure that Use network name for automatic user log in is selected.

Synchronizing a SharePoint team Web site or FrontPage-based Web site with a Visual SourceSafe project

After you have installed Microsoft Visual SourceSafe 5.0 or later and established the user and group accounts that will have permissions to use the Visual SourceSafe project, you must synchronize the Visual SourceSafe project with your SharePoint team Web site or FrontPage-based Web site. To synchronize your SourceSafe project, you use the Configure Version Control page in the Site Administration pages.

To view the Site Administration page 

  • If you are a server administrator, on the server computer click Start, point to Programs, point to Administrative Tools, click Microsoft SharePoint Administrator, and then on the Server Administration page, click the name of the site you want to manage.

  • If you are a site administrator, on your Web site, click Site Settings, and then under Web Administration, click Go to Site Administration.

To synchronize a Visual SourceSafe project 

  1. On the Site Administration page, click Configure version control.

  2. On the Configure Version Control page, select Use external version control (Visual SourceSafe only).

  3. In the text box, type the name of the Visual SourceSafe project you want to use. Type $/ followed by a project name, as in $/rootweb.

  4. Click Submit.

If the project does not already exist in Visual SourceSafe, it is created, and all files in the Web site are checked in. If the project already exists, the SharePoint team Web site or FrontPage-based Web site and the project are merged. Any file in the SharePoint team Web site or FrontPage-based Web site that is in an ambiguous state (such as a file that has the same name as a file in the Visual SourceSafe project but that was never in the Visual SourceSafe database) remains checked out.

Once a SharePoint team Web site or FrontPage-based Web site is synchronized with a Visual SourceSafe project, all files in the Visual SourceSafe project will be displayed in your Web page editor with a green dot (to indicate that the file is checked in) or a red checkmark (to indicate that the file is checked out).

Enabling built-in source control

You can enable the source control built into SharePoint Team Services or FrontPage 2002 Server Extensions on Windows Server 2003 (FrontPage 2002 Server Extensions only), Microsoft Windows 2000 Server or Professional, or Microsoft Windows NT Server 4.0, or on FrontPage 2002 Server Extensions on UNIX with FrontPage-patched Apache Web server. To enable built-in source control, you use the Configure Version Control page in the Site Administration pages.

To view the Site Administration page 

  • If you are a server administrator, on the server computer click Start, point to Programs, point to Administrative Tools, click Microsoft SharePoint Administrator, and then on the Server Administration page, click the name of the site you want to manage.

  • If you are a site administrator, on your Web site, click Site Settings, and then under Web Administration, click Go to Site Administration.

To enable built-in source control 

  1. On the Site Administration page, click Configure version control.

  2. On the Configure Version Control page, select Use built-in version control.

  3. Click Submit.

Cc768013.spacer(en-us,TechNet.10).gif

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft