Checking In Packages and Elements

The VCS Integration feature adds packages and elements to your VCS when you apply the Check In or Check Out command to a file, a folder, or a package.

Keep the following points in mind when checking packages, folders, and elements into a VCS:

Because the VCS Integration feature does not work with all files in the Integration Server directory structure, use the VCS client to manually check in any of the unsupported files that it uses (such as dynamic server pages, HTML documents, templates, and configuration files). For more information, see Configuring the VCS Integration Feature.

Although packages and folders are never shown as checked out in the Package Navigator view, you can apply the Check In command to a package or folder to check in all of the elements within the package or folder.

If your package contains C/C++ services, you must check in those services manually with your VCS client.

When you check in a package or element to ClearCase, the check in is performed on the branch of the package or element that is currently present in the underlying view.

If a package or element does not exist in the VCS, applying the Check In command adds the package or element to the VCS repository. For more information about this behavior, see Adding New Packages and Elements to a VCS.

If a package or element has unsaved changes applied to it, you must save the changes to the package or element before you can check it in.

1. In Package Navigator view, right-click the package, folder, or element that you want to check in, and select Check In.

2. In the Comment for Check In dialog box, enter a comment that describes the changes made to the package or element. This comment will be displayed in the revision history for the element. If you do not enter a comment, the revision history will display only user, time, and date information for this check in.

3. Click OK. The small check mark is removed from the right of the package or element’s icon in the Package Navigator view.

If the version of the file you checked out is not the same as the one that is currently available, another user has checked in the file in between. Your check in will not be done and an error message will be displayed.

If you check in a package that existed before VCS Integration, the manifest.v3 file will not get checked into the VCS.

If you have made no changes to the package, folder, or element, the comment you enter will be ignored by Visual SourceSafe unless you configure Visual SourceSafe to check in unchanged files.

Checking in a package with many elements might take a significant amount of time. Designer will not be available during the check in procedure.