WXS123

What should the entries look like in the projects and solutions for source control binding with TFS We have seen everything get marked as "SAK" sometimes and other times with a specific GUID and server http address. Which one is right It seems if it is mixed in a solution it gets very confused and starts asking to checkout varying projects and the solution for edit and even if it does, does not update the bindings...



Re: Team Foundation Server - Version Control Project and solution source control binding?

Mario Rodriguez- MSFT

Hi:

If the project is added to source control along with the solution, then the settings are SAK ("should already know") because the solution has the necessary binding information.

If the project is added to source control by itself then the binding info will contain the TFS server URL "hint" and the absolute server path of the project.

If you have a reproducible scenario where a project with bindings other than SAK is causing checkouts, we would be happy to take a look.






Re: Team Foundation Server - Version Control Project and solution source control binding?

WXS123

Ah, ok, thanks. Yes I believe if you have mixed bindings some with SAK and other projects with the specific bindings it gets very confused. I'm sure we'll hit this again in the near future and will contact when we see it again. To resolve I edited out all the bindings from solution and project and rebound so all projects got SAK instead of mixed bindings that seemed to solve the problem. Until we did that it kept asking to checkout some projects and the solution but never actually modified them to resolve, even when we manually rebound with Change Source Control dialog, only manual notepad editing resolved.

Thanks