In order to bring over some files from source control into my XP-Moded instance of Visual Studio 2003, I was able to bring over some of the files from source control by selecting (in Visual Studio 2003) File > Source Control > Open From Source Control...attaching to the TFS server, navigating to and then selecting the desired project.
However, that operation did not bring over the *.sln file, so I am not able to open that project (the *.cs file is there, but not its "host" sln file).
I then tried to attach / bring over the missing files via File > Source Control > Team Foundation Server MSSCCI Provider
On doing this, I am warmly (I think) welcomed by the "Visual Studio Conversion Wizard" but, although it seems to work, it doesn't bring over the *.sln file either, purportedly because the *.sln file was created with a different version of VS (so it seemingly gleefully tells me) -- no doubt it's talking about the VS 2003 / VS 2010 (shell) mismatch...?
So the local folder where I am attempting to put the files is missing *.sln:
The *.sln file does exist in the TFS server area - when I select File > Source Control > Open from Source Control > Connect to a Team Foundation Server > Expand the folder dialog > Navigate to the project I want, this is what I see:
...but highlighting, and even 2-clicking, HUtilCE.sln does not transfer it to the Filename combo box - I have to manually type it into there, but then when I mash the "Open" button I get, "Unspecified error."
So which hoops, and in which order, must I jump through to attach to this project; and what grade of fire retardant should I spray on my tail before taking that fiery plunge?