First off: Major gripe here; Why would I need to purchase VSS2005 if we just shelled out $8000 for TFS and CAL's?

What do I need to do to get this to work? Can anyone tell me how I do the VSS2005 setup? I have tried searching through the forums here with no end.

Furthermore: I don't have the MSDN access level to download VSS2005 as it would appear others have resorted to. I tried the VS2005Team 180day trial, but cannot find VSS2005 there either. I have re-installed TFS. I have also tried the beta service pack to no avail. I have spent (wasted) countless hours hunting for the elusive VSS2005 install.

Oh, TFS itself works fine... just need sourcecode..

Please, Please help,

-David

The reason for the dependency is that the VSSConverter uses some APIs that are only available in VSS2005.

I believe the reason they let that dependency go though was that all the SKU's that include TFS also included VSS2005.

So what SKU did you buy?

Here is the info I have from our invoice and from the CD's themselves.

Product Code 126-00095 OPEN Visual Studio Foundtion SVR 2005 LICENSE (End Item Part No.125-00371 )includes CD's x12-15894, x12-15898, x12-15901, x12-15905, x12-15908, x12-15911, x12-15914, x12-15917.

The CD's were actually part of a "$25 WWF VSTDIO FND SVR 2005 WIN32 CD Disk Kit" 125-00371

Also the U-CAL's at 126-00139

Hope this helps,

-David

To tell you the truth, none of that means anything to me(Althoguh it probably includes the information I was asking for).

What I meant was, did you TFS come with one of the Visual Studio Team System products? (Visual Studio 2005 Team Edition for Software Testers, Visual Studio 2005 Team Edition for Software Developers, ect.) , With Visual Studio Pro?

If you dont know, Ill ask around and see if i can get the cd numbers translated into english; and find out if any of them should have VSS.

No, we purchased Team Foundation Server independantly for a dedicated single server install.

http://msdn.microsoft.com/vstudio/teamsystem/products/tfs/ I think that is what we have.

-David

Well, I guess there is no solution other than to make sure you either have the appropriate MSDN level to Download VSS2005 or to pay the additional $500 for VSS2005 when you buy TFS.

I gave up and just ordered VSS2005.

If someone from the VSS/TFS team is reading this: It would be nice next time around if you could NOT make the VSS6>TFS upgrade/converter application dependant on a unrelated piece of software (VSS2005).

You wouldn't buy a Mercedes Benz if the dealership also mandated you buy a Chrysler product so the Mercedes would run, would you?