If you were using Team Foundation prior to Beta 3, you most likely have solutions that were bound to Team Foundation using source control intergration. Although we don't support 'upgrading' from Beta 2 to Beta 3, you could have manually copied your data from a previous database into the new new one by means of checking in your old files to the new server. If that's the case, then you will encounter problems when trying to open you solutions using Visual Studio 2005 RC1 w/ Team Foundation Beta 3. These issue arise from the fact that we made significant changes to how we handle source control integration for Team Foundation. However, all is not lost! There are a couple of ways that you can recover your source control bindings without too much headache.

The first option is the easiest. Upon opening your solution, you should receive a message box asking how you would like to work with the solution. This message is stating that Visual Studio could not load the source control plug-in for your solution and we must either work temporary disconnected -or- remove the source control bindings altogether. For this first scenario, you can select to remove the source control bindings. After the solution has successfully opened, you can then select File > Source Control > Change Source Control... This will bring up the Change Source Control dialog which will allow you to bind the solution to your new Team Foundation server.

The second option involves editing the solution file manually before you attempt to open it using Visual Studio. Within the solution file (*.sln), you will find a section which looks like this:

GlobalSection(SourceCodeControl) = preSolution
  SccNumberOfProjects = 4
  SccEnterpriseProvider = {DE9DF59E-8859-48A8-AA95-1E984B3B48A9}
  SccTeamFoundationServer = http://vstsb2:8080/
  SccLocalPath0 = .
  SccWebProject1 = true
  SccProjectUniqueName1 = http://localhost:2005/adventureworks
  SccProjectName1 = adventureworks
  SccLocalPath1 = adventureworks
  SccProjectEnlistmentChoice1 = 2
  SccProjectUniqueName2 = Notification\\Notification.csproj
  SccProjectName2 = Notification
  SccLocalPath2 = Notification
  SccProjectUniqueName3 = TestProject\\TestProject.csproj
  SccProjectName3 = TestProject
  SccLocalPath3 = TestProject
 EndGlobalSection

The trick to fixing the problem is in changing the values in RED. The GlobalSection name has been changed from SourceCodeControl to TeamFoundationVersionControl, and the SccEnterpriseProvider GUID has been changed from {DE9DF59E-8859-48A8-AA95-1E984B3B48A9} to {4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}. So, after editing the file, this section now looks like this:

GlobalSection(TeamFoundationVersionControl) = preSolution
  SccNumberOfProjects = 4
  SccEnterpriseProvider = {4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}
  SccTeamFoundationServer = http://vstsb2:8080/
  SccLocalPath0 = .
  SccWebProject1 = true
  SccProjectUniqueName1 = http://localhost:2005/adventureworks
  SccProjectName1 = adventureworks
  SccLocalPath1 = adventureworks
  SccProjectEnlistmentChoice1 = 2
  SccProjectUniqueName2 = Notification\\Notification.csproj
  SccProjectName2 = Notification
  SccLocalPath2 = Notification
  SccProjectUniqueName3 = TestProject\\TestProject.csproj
  SccProjectName3 = TestProject
  SccLocalPath3 = TestProject
 EndGlobalSection

One last thing. You should also delete any *.suo files what you have associated with the solution. This file contains user cached settings and can be safely deleted.

Hope this helps you in getting up and running with Team Foundation Beta 3. Let me know if you have any problems with this solution.