C# 2010 upgrade problem?

Question

Note: I asked this question in a team server foundation forum since the issue is both C# and probably FTSF.

I have obtained an asp.net 2010 web forms file from another company that we are suppose to share the code. This other company uses team server foundation for the source control and my company will be using some source control in the future. When I opened the code in the past, there were references to team server foundation. Now when I open the code I am getting the following error message:
 
"Unable to open 'C:\users\myname\documents\visual studio 2010\projects\sup\support.vdproj".
 
My workstation has the latest visual studio 2010 upgrades which includes the SP1 release.
 
When I look on the internet for what my problem is, I see links like the following:
 
http://connect.microsoft.com/VisualStudio/feedback/details/650587/vs-2010-sp1-changes-packagecode-in-vdproj-on-each-build-but-fails-as-source-controlled.
 
I am guessing that my error is related to the VS2010 SP1 upgrade that has more control on setup and deployment packages that are under team server foundation, correct?  If this is the case, do I need to remove the team server foundation 'hooks' from the visual studio.net projects that I am working on? If so, can you tell me and/or point me to a reference that will remove the team server foundation hooks?
 
If this is not the solution, can you tell me and/or point me to a reference that I can use to solve my problem?

Answer 1

If you aren't using TFS then there is no reason to have the bindings set up.  Note however that the bindings are stored in the files so removing them will remove them for everyone.  To remove the bindings use File\Source Control\Change Source Control.  Then unbind the solution and all the projects. 

As for the Connect issue there is a hotfix to resolve it.  If you apply that fix then the problem should go away.

Michael Taylor - 4/11/2012
http://msmvps.com/blogs/p3net

Answer 2

What is the hotfix that I can use? Can you point me to a url that will solve the problem?

Answer 3

From the Connect ticket: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=35848
Code Gallery: http://archive.msdn.microsoft.com/KB2529927