Troubleshooting
Problem
This technote provides information about discrepancies between the source control information in the solution file and associated projects that can cause errors and warnings when attempting to open projects in Microsoft® Visual Studio .NET while integrated with IBM® Rational® ClearCase® using Visual Studio Industry Partner (VSIP) bindings.
Cause
This issue is seen if the integration between ClearCase and VS .NET is broken or if the solution file and projects were not converted properly to use VSIP bindings if the solution file and projects were developed in a previous integration of ClearCase and VS .NET.
An upgrade of ClearCase from version 2003.06.15 (SR5 and all previous versions) to version 2003.06.16 (SR6 or later including version 7.x) while retaining the same version of VS.NET will require the solution file and projects to be converted to use the new integration model and binding configurations.
The bindings and source control information referencing each project associated to a specific solution do not contain the same information for the correct source code control provider.
For example, if a solution file contains the following lines in its Global Section for source code control provider...
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Developer|Any CPU = Developer|Any CPU
Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
{8C76B954-5AE2-48D3-9996-012EF78CC5B3}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{8C76B954-5AE2-48D3-9996-012EF78CC5B3}.Debug|Any CPU.Build.0 = Debug|Any CPU
{8C76B954-5AE2-48D3-9996-012EF78CC5B3}.Developer|Any CPU.ActiveCfg = Release|Any CPU
EndGlobalSection
...and its associated project files such as .csproj, .vcproj, .... contain the following lines...
<SccProjectName>Rational ClearCase</SccProjectName>
<SccLocalPath>Rational ClearCase</SccLocalPath>
<SccAuxPath>Rational ClearCase</SccAuxPath>
<SccProvider>Rational ClearCase</SccProvider>
...then attempts to open specific projects results in the following error and warning messages:
Note: The main difference between the two files is that solution file does not contain the correct information regarding its source code control provider while the project file does contain the correct information.
Source Control
i "There appears to be a discrepancy between the solution's source control information about some project(s) and the information in the project file(s).
To resolve this discrepancy it will be necessary to check out the project file(s) and update them. If the check out fails, however, and the solution is closed without saving, you will see this warning again the next time you open the solution."
Microsoft Visual Studio
! "The project 'controlJobBuilder' is under source control. An error occurred registering this project with source control. It is recommended that you do not make any changes to this project."
Microsoft Visual Studio
! "Unexpected error encountered. It is recommended that you restart the application as soon as possible.
Error: The parameter is incorrect.
File: vsee\lib\xfcstr\winstrw.cpp
Line number: 166"
Note: Simple indicators that ClearCase and VS .NET are not integrated correctly, seen in this type of situation are:
- The ClearCase Menu Option does not appear at the top of the VS.NET IDE
- The Front Desk is not shown as an additional Tab next to Start Page when the VS .NET IDE is open
- There is no Rational ClearCase tree structure in the left hand side of the Tools > Options menu
Resolving The Problem
- Verify that ClearCase and VS .NET are integrated correctly using the indicators mentioned above.
- If the two applications are not integrated correctly, then follow the procedure in technote 1259189 on how to integrate the full ClearCase client with VS .NET 2003/2005 or technote 1319889 for integrating the CCRC plug-in with VS .NET 2005.
- Once the two applications have been successfully integrated then the projects must be converted to use the new VSIP bindings. Follow technote 1254745 on how to convert projects that were created using the old MSSCCI bindings. This is necessary in order for the solution file and projects to continue to be used after an upgrade requiring the bindings to be changed to reflect a new source code control configuration.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21267165