I have a couple of problems that I suspect may be related.

Can you run ListTeamProjects.exe against the server from both the TFS server itself and your machine?

You can find it in the zip file that's attached to this post:

http://blogs.msdn.com/jmanning/archive/2005/10/14/481105.aspx

Here are the results of running ListTeamProjects against the server from both the server and my machine:

View from my development workstation (highlighted projects I can't see from Team Explorer):

C:\...\Debug>ListTeamProjects.exe http://WAL1CD258:8080
All team projects (8):
ODWin vstfs:///Classification/TeamProject/3cedfa2f-67b2-4653-90f7-0772ba0ff3bc [WellFormed]
Branches vstfs:///Classification/TeamProject/2e58eb85-5636-4e2c-8cd7-2380a7eeb872 [WellFormed]
CMDWinTestingSoln vstfs:///Classification/TeamProject/aca04d14-677f-46a6-b538-28542e241c01 [WellFormed]
TestBranchApp1 vstfs:///Classification/TeamProject/6b41a3b7-f897-42a7-93ed-45dd8c5164d0 [WellFormed]
CMDWinDemo vstfs:///Classification/TeamProject/c2e66608-aa7d-47de-aa26-49d454db90ff [WellFormed]
FCMUtil vstfs:///Classification/TeamProject/5c18395c-4dea-4cd7-af63-8038badd9ae1 [WellFormed]
CMDWin vstfs:///Classification/TeamProject/b81e7910-4abe-4a0b-89da-d787a04b9c1c [WellFormed]
TestBranchApp2 vstfs:///Classification/TeamProject/d94d3932-1303-4703-a113-e4359ae57f3e [WellFormed]

C:\dmadrian>ListTeamProjects http://WAL1CD258:8080
All team projects (8):
ODWin vstfs:///Classification/TeamProject/3cedfa2f-67b2-4653-90f7-0772ba0ff3bc [WellFormed]
Branches vstfs:///Classification/TeamProject/2e58eb85-5636-4e2c-8cd7-2380a7eeb872 [WellFormed]
CMDWinTestingSoln vstfs:///Classification/TeamProject/aca04d14-677f-46a6-b538-28542e241c01 [WellFormed]
TestBranchApp1 vstfs:///Classification/TeamProject/6b41a3b7-f897-42a7-93ed-45dd8c5164d0 [WellFormed]
CMDWinDemo vstfs:///Classification/TeamProject/c2e66608-aa7d-47de-aa26-49d454db90ff [WellFormed]
FCMUtil vstfs:///Classification/TeamProject/5c18395c-4dea-4cd7-af63-8038badd9ae1 [WellFormed]
CMDWin vstfs:///Classification/TeamProject/b81e7910-4abe-4a0b-89da-d787a04b9c1c [WellFormed]
TestBranchApp2 vstfs:///Classification/TeamProject/d94d3932-1303-4703-a113-e4359ae57f3e [WellFormed]

1) can you try to connect with VS as another user on the same development workstation and see if they see the highlighted projects?

2) Is there another TFS instance around that your VS client may instead be talking to? We've seen customers that did a "move" via backup/restore and some clients were still talking to the "old" TFS instance, so I want to rule that out.

Thanks!

Since it's sounding like a cache problem, the overkill route to fixing it should be to blow away your local TFS cache dir (with VS not running)

You should be able to find it at %USERPROFILE%\Local Settings\Application Data\Microsoft\Team Foundation\1.0\Cache

If that doesn't work (you still can't see the new projects), please let us know.

James,

Thanks very much for pointing out this cache problem because clearing the cache and then starting Team Explorer allowed me to view the projects I had added before, as well as new projects I added in the current session.

However, I'm noticing something else that appears to be a cache problem. I have two instances of TFS available, each with different projects. When I connect to TFS #1, I see the projects from that server, even when I disconnect and log on to TFS #2. Likewise, if restart VS, clear the cache again and connect to TFS #2 intially, I see the projects from TFS #2, even when I disconnect from #2 and connect to TFS #1.

It's as if the cache is holding onto the content from the first server it sees, but isn't letting go after that. Is it possible that I have something set up wrong that is causing my caching not to work properly? If there's not a way to make this work, I'm wondering if disabling caching (if that's possible) is another option to consider.

Thanks again for all your help.

David

Is there any chance one of those TFS instances was created by doing a restore of a backup of the other?

We have a couple pieces of identifying information for each TFS instance (GUID's identifying the instance) and usually you see that kind of symptom when 2 servers both have the same ID's, so when we cache the information on the client (and the cache is keyed by that GUID), you see this kind of problem.

That's exactly the case. I checked with our administrator and he says that he did create the other TFS instance by restoring a backup of the other server.

I think I'm pretty well squared away on this question. Thanks again!!

Great - thanks for the confirmation.

You can actually use one of the tools installed in the AT's Tools subdir to "re-stamp" the second (created as clone of first) instance. See Dan Kershaw's answer in this thread which details the steps:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=698261&SiteID=1

That's great we can "re-stamp" the other TFS server to give it a unique name rather than possibly having to reinstall it.

Thanks again. You've been a huge help.

David