IBM Support

Projects created with VS.NET in an automatic view in a view extended path are not recognized as being in ClearCase control when you add project artifacts to source control

Troubleshooting


Problem

In the case where you are creating a VS.NET solution/project in an automatic view using the fully qualified view extended path (such as R:\view_tag\vob_tag\solutionpath), the integration fails to automatically update the .sln and .vcxproj files to enable the ClearCase integration for the solution/project and its artifacts. Without the additional metadata that the integration normally provides, VS.NET does not recognize the project as being under source control, and the ClearCase functionality is not available for manipulating the artifacts. []Note:[] This issue does not occur if the view root has been SUBST'd to a drive letter (for example, []subst T: R:\view_tag[] from the DOS prompt). Using []T:\vob_tag\solutionpath[] during solution/project creation in VS.NET will circumvent the problem. The web, dynamic, and snapshot view types are unaffected.

Cause

Changes made to the VS.NET integration to accommodate the use of the SUBST DOS command for automatic view paths where you can substitute a drive letter for the automatic view root caused this regression to the project creation use case under view extended paths for automatic views on Windows systems.

Environment

Windows

Resolving The Problem

The problem occurs only if you have created a new project using the fully qualified, view extended, automatic view path.

This issue can be worked around by using one of the following methods:

  • If using automatic views, after the view is started, use SUBST to map a drive and create new projects using the SUBST'd drive path. For information on how to do this, refer to technote http://www.ibm.com/support/docview.wss?uid=swg22010563.
  • Use a different view type such as a web, dynamic, or snapshot view to create projects that others can import/open using a fully qualified automatic view path.
  • For projects that end up in this situation, it is possible to salvage them by manually adding the required metadata. To accomplish this, you can use CTE (in VS.NET open ClearCase Front Desk and navigate to Tools > ClearTeam Explorer and select the ClearCase Explorer icon). Then you can use CTE to navigate to the location of the project and check out the .sln and .vcxproj files:
    1. For the .sln file, on line 6 (in the "Global" section) add the following metadata:

        2. GlobalSection(RationalClearCase) = preSolution

        SourceControlProvider = RationalClearCase
        EndGlobalSection

    2. For the .vcxproj file, locate the XML container <PropertyGroup Label="Globals">. Immediately after the <RootNameSpace>...</RootNameSpace> container, add the following metadata:

        3. <SccProjectName>Rational ClearCase</SccProjectName>

        <SccAuxPath>Rational ClearCase</SccAuxPath>
        <SccLocalPath>Rational ClearCase</SccLocalPath>
        <SccProvider>Rational ClearCase</SccProvider>

    3. Check in both files.
    4. If you have opened CTE from VS.NET Front Desk, shut down CTE and restart VS.NET. When you reopen the solution/project, the ClearCase functionality on the project should be restored.
Note: Because the issue is due to incorrect handling of metadata, the use of view extended paths in automatic views is unaffected if the .sln and .vcxproj file already contain the correct metadata. Such projects might still be imported using the full view extended automatic view path with the expectation that the ClearCase menus and operations will function.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Integrations: Visual Studio.NET","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.0.1.2;9.0.0.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg22011468

Page Feedback