An additional benefit of creating projects is that you can more easily manage project files in a source control system. You can establish a relationship between a source control application and your project, so that you can manage check-out, check-in, and other source control operations without opening the source control application.
Version source control for Web site content is an essential for coordinating team development of complex projects. A source control system does add a layer of file management responsibility, but it offers clear advantages for developers, managers, and support staff. Source control enables team members to do the following:
Source control systems really are about control; they are designed to control file management in application development and related work. Common terms, such as check-in, check-out, lock, and unlock, accurately describe the security procedures required for an effective source control system.
HomeSite uses the Microsoft-published interface called the Source Code Control (SCC) API to connect with a wide range of standard source control products; it can work with both client-based and server-based systems.
HomeSite automatically generates a list of source control applications detected on your system when you first select the Choose Source Control Provider command for a project. You can then select the appropriate provider from the list.
The user interface and command structure for source control applications varies from vendor to vendor, so check the documentation for your source control software for specific procedures and options.
There are three basic steps to establishing a relationship between your HomeSite project and your source control application. Note however that the exact procedure differs, depending on your source control application.
Otherwise, HomeSitecannot detect it.
To start, right-click on the project root, select Source Control, then select Choose Source Control Provider.
To start, click Map Project to Source Control button.
For more information, see Knowledge Base article 14802.
The following procedure takes you through the steps of creating a Microsoft Visual SourceSafe∆ (VSS) project, and then placing your HomeSite project files under VSS source control.
Visual SourceSafe uses the term project to refer to a distinct set of files stored in its database, so this procedure uses the term VSS project to distinguish it from a HomeSite project.
A list of the source control applications detected on your system appears.
You might be required to login to VSS at this point.
The relationship between the source control application and HomeSite project is established.
You can control your source directly from HomeSite or, if you must work directly in the source control application, you can open it from HomeSite.
The Source Control toolbar contains buttons for working with a version source control system, for example to check in, check out, and add to source control. The toolbar commands are applied to the current document in the document window.
You can also access the toolbar commands by right-clicking in the Projects pane.
You cannot add a file to source control unless it is located in the physical directory of a project that has been mapped to a source control application.
If the options on the toolbar are disabled, open a project that is mapped to the source control application. This establishes a connection for the duration of your session.
Knowledge Base article 14856 covers the steps required to set up multiple user access to project files in source control.
If you are responsible for setting up Visual SourceSafe access to files for multiple users, you should consult Knowledge Base article 16754