• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1761
  • Last Modified:

Discrepancy between solution's source control and the project file in Team Foundation Server 2010

I recently converted over from Visual SourceSafe to Team Foundation Server 2010. All went through ok, but only afterwards I'd noticed I hadn't checked in all projects in the VSS directories. No big drama, until I created a working folder for a particular reporting services solution I was working on (have to access this in Visual Studio 2008 so installed the necessary plug-ins for this). I get the following error pop-up when I start up the solution:

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.

Open in new window


Following these instructions though doesn't work as I get the same error popping up when I go back in.

Any ideas how to fix please?
0
Grffster
Asked:
Grffster
1 Solution
 
Ryan McCauleyData and Analytics ManagerCommented:
Have you tried unbinding and rebinding the solution (or the affected projects)? The upgrade from VSS to TFS changes the bindings on all the projects to use the TFS provider instead of VSS. However, since you had some changes out that weren't checked in, your local copy still likely has the old provider in the project binding info.

From the file Menu, select "Source Control" and then "Change Source Control", and unbind the offending project. Once it's unbound, you can attempt to re-binding it (it may ask you to pick a folder in TFS to bind to), and that should update the info in the project to resolve this issue.

Alternatively, you can attempt to do a "Force Get" on the project file itself (not the whole project, since you've made changes you don't want to lose) using the Source Control Explorer. The project file in TFS would have had its bindings updated properly, but since you've got a local copy you're working with, it may just be the local copy that's out of date, and fetching a new copy of the just the project file may update the bindings properly as well.
0
 
GrffsterAuthor Commented:
When I opened up VS2008 to try this out on the offending solution, it had miraculously cured itself! However I tried it on a similar solution with the same issues and it didn't seem to work. Good suggestions though. Think I'll just live with it for now and see if that one corrects itself in the end too.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now