Well, after more tries than I can count, I have finally successfully created a Visual Studio Team Project.
I had installed on one virtual pc serving as the server and domain controller Team Foundation Server, and a second virtual pc serving as the Client Team Suite, as well as a member pc on the domain of the other virtual machine.
What I didn't realize was:
* Promote the server to domain controller BEFORE anything else.
* Install sharepoint services 2 AFTER installing SQL 2005 April CTP.
* Don't forget that a FQDN will look out on the net for your domain controller before it scans the local net.
This one was rough -- my domain pc was called merlin2003.devnet.jnadal.com and my static ip on a virutal-lan called "Devnet" was 10.237.0.17. However it was always resolving to the name of my real host: jnadal.com since that was the domain of the FQDN for my Domain Controller.
To fix this, you can add an entry to the hosts file, but only if the current user (I was a domain user), was an administrator on the MACHINE (not just the domain) which was pinging merlin2003 (the DC). Once you log on as a machine admin, you can add the hosts entry, and then Team Suite can create a project.
My main gripe with team system, and the one that's costed me the most time so far is that even if you add a Team Foundation Server by ip address within Visual Studio, it will still ping out to the web services for project creation / report creation (Rosetta) / Source Control Creation (Currituck?) etc. by machine name, rather than ip.
Possible Solutions (These links helped me after some googling):
Tried to create a Team Project in Team Suite, but got an error message: "No user identity info returned from GSS"
I read on dbrowning's blog in his post that he also got it. Kent Sharkey responded that there's an install guide:
I guess I still have some reading to do...
Here's the first of what I hope to be many posts on Visual Studio 2005 Team System / Team Foundation Server.
My scenario is my "Betabox," that is a pretty beefy box that runs Virtual Server, with a 2003 VM running Yukon/TFS and an XPSP2 VM running VS2k5 Team Suite.
First impressions so far? I love the installer for SQL2005, but the TFS installer needs more work. It told me I didn't have sharepoint services installed, but never told me where I needed to get them from / if I had to pay, etc. So here's a tip / link for anyone in the same boat:
On this page, you'll find a download link for the necessary Sharepoint services: http://www.microsoft.com/windowsserver2003/techinfo/sharepoint/wss.mspx
On that same page, there's a quote that says it's a free license if you have a license for Windows Server 2003: (Thank you NY .NET Developer UG!)
"Licensing.Windows SharePoint Services is provided as part of the Windows Server 2003 operating system and Windows licensing terms apply to its use. There is no additional charge for Windows SharePoint Services."
Wierdness #2: Installing SQL2005 installs Visual Studio... this surprised me quite a bit... It looks like they did this so you could create report projects, analysis projects, etc.
My last comment for now is that after installing TFS, there's nothing. It doesn't install anything in start. It doesn't give you any hints on where to go to further set it up / use it. This really surprised me. It's set up a bunch of virtual directories, but I haven't tried connecting to it from my XP client VM yet. So far there has been no install issues that I couldn't resolve.
Actually the toughest part so far has been connecting the 2003 Virtual Machine to the outside internet, followed by the long list (42 updates!) of Windows Update installs. (Visual Studio 2005 requires Windows Installer 3.1 to be on the machine before the install will start.)