This is a follow-up to my last post where I'll talk about the highlights and lowlights of our TFS deployment project.
So how were the requirements met?
And what didn't work as expected? Well, there were a few bumps along the way...
So how did it pan out? You'll need to read my next post to find out.
Brian Harry on Promised SP1 docs and Last Word on TFS Expirations (I Hope). YuTong on How to Enable...
Great if you could throw some light on the following.
1. How did you change the version control integration used in TFS? We also have a custom build set up and I want to integrate the build numbers from this system.
2. The MSSCCI Provider for 2003 asked for credentials and failed to validate. We dont have any forest issues as you mentioned.
1. From a build perspective, we had to be able to label the latest source (with the build id), retrieve it and then build it. All of this was done by coding against the TFS client object model. The basics are outlined in http://msdn.microsoft.com/library/en-us/Extensibility_Guided_Tour/The%20Version%20Control%20Object%20Model.asp
2. I haven't seen a credential validation issue with the provider (other than the usual suspects). If you're able to hit TFS with Team Explorer, you should be able to use the MSSCCI provider from VS2003. Our forrest issue was solved by simply setting the Login ID (in domain\username format) on Tools->Options->Source Control->SCC Provder.