Monday, May 05, 2008
« Don't be a SCRUMBUT! | Main | Bugs on an Agile Team »

OK, so this one isn't about agile. But, it's such an annoying pain point I thought I would share. And, I couldn't find much info on this error message out there in the ether.

Visual studio complains every time the solution is opened: "... discrepancy between the solution's source control information ..."

When using Team Foundation server for source control (also the same issue with VSS I presume), someone on my project decided it would be better to use the source control server's IP address in the project SccAuxPath entry, instead of the server's name. They may have been experiencing DNS issues, or something like that. I recommended to the team that if this were the case, and DNS was not dependable, to put the IP and the server name in their c:\WINDOWS\system32\drivers\etc\hosts table. This "discrepancy" confuses the poor little source control system, and it senses that there is a difference between the server's name (to which it has a TCP connection already) and the target destination specified in the project.

So, it checks out the file, expecting that it will have to change something. Then, it is able to connect using the IP, and everything's fine. Except, the files are left checked out with no changes.

 

Here is the fix:

 

simply change

    <SccAuxPath>http://10.10.10.10:8080</SccAuxPath>


to

    <SccAuxPath>http://TFSSERVER:8080</SccAuxPath>


and problem is solved.

 

Just remember that TFS is relatively easy to confuse... Now, just go ahead and retire TFS and use Subversion like the rest of us ;-)

Monday, May 05, 2008 11:57:08 AM (Pacific Standard Time, UTC-08:00)  #    Disclaimer  |  Comments [4]  |  Trackback Related posts:

Monday, May 12, 2008 5:11:56 AM (Pacific Standard Time, UTC-08:00)
I've been investigating this very same issue. We have a bunch of people from outside the company VPNing in and I figured first of all this is what was causing the problem.
However, we've tested this with a guys outside on a separate (new) project and it doesn't cause the problem. Wierd thing is that the entry on this new csproj is:

<SccAuxPath>SAK</SccAuxPath>

Which works perfectly for me onsite who used to only get the IP, another guy onsite who used to get the server name and the chaps on the other side of the VPN. I've traced all of this back to a checkin sometime earlier in the year that changed all of the SAK entries to what we have now. That's the point where this "to-ing" and "fro-ing" began.
I have yet to work out what caused the change from SAK -> to all of this nonsense though....
Jax
Monday, May 12, 2008 5:13:21 AM (Pacific Standard Time, UTC-08:00)
I'd also like to add that i'd rather be using subversion too. :)
Jax
Monday, May 12, 2008 5:29:32 AM (Pacific Standard Time, UTC-08:00)
Oh and this explains what SAK means.

http://alinconstantin.blogspot.com/
Jax
Monday, May 12, 2008 7:08:43 AM (Pacific Standard Time, UTC-08:00)
Thanks JAX - that link looks like a good place for info on TFS.
John Boal
Comments are closed.