There are plenty of posts scattered around the web about the authentication of clients against Team Foundation Server from Visual Studio. Either you get prompted for credentials when you don't want them, or you can't get it to prompt for credentials when you need to supply something different.
I've been having a similar issue - whenever I start Visual Studio on any one of four different machines, I get prompted for credentials for TFS. Boo!
The problem stems from the fact that Visual Studio doesn't hold the credentials. The OS holds the credentials and associates them with your user account.
If you're using XP, look in Control Panel / User Accounts / Advanced, and you'll find a button labelled Manage Passwords. For Vista users, it's Control Panel / User Accounts / Manage your network passwords.
Either way, you get to a dialog box titled "Stored User Names and Passwords" which lists sites for which credentials have been recorded. They usually get stored when you select one of those innocuous 'Save Password' options.
Now, I thought I was set up perfectly well. Because I access TFS both locally and remotely, I'd already stored credentials using the fully-qualified domain name (FQDN) of the server, tfsserver.hastobe.net (don't bother trying it; I've changed the name for the sake of illustration).
I've configured the server in Visual Studio using the same FQDN.
All made sense to me but for some reason, I was still getting prompted every time I logged in.
Searching around, I really didn't find anything that I didn't already know. All of the posts I came across pointed me to the "Stored User Names and Passwords" dialog.
So, by way of an experiment, I added another entry to the dialog, this time using just the server name, tfsserver. Lo-and-behold, the next time I started Visual Studio, there was NO PROMPT and I was connected to TFS automatically. Hoorah!
It doesn't make a great deal of sense to me, and I'm skeptical that it will work when I'm connecting remotely. I'll find out over the next couple of days when I'm out and about and post an update. It's worth mentioning that my TFS server is in a workgroup. One client is in the same workgroup as the server, two in different workgroups and a fourth in a completely separate domain.
Aug 25 2008, 10:40 PM