mardi 8 mai 2012 16:46
We had Visual Studio 2010 Ultimate Service Pack 1 installed on the Windows Server 2008. On the same box we have TFS 2010 installed and configured. Everything worked fine in terms of connecting from Visual Studio to TFS version control and running some builds.
Then we were unable to run one build for the SilverLight 4 project. The solution we've found was to install SilverLight tools for Visual Studio 2010. After we installed the tools, we were not able to connect from Visual Studio to TFS Version Control anymore.
The error thrown is "Method not found: 'Boolean Microsoft.TeamFoundation.VersionControl.Client.Workspace.OwnerNameMatches(System.String)'."
The problem is described in this blog:
We've tried the suggested solution to uninstall SP1, then VS 2010, then install back Visual Studio and SP1. The error is still there.
What is the solution to our problem?
- Déplacé Bob_BaoMVP, Moderator mercredi 9 mai 2012 02:06 (From:Visual Studio Source Control and SourceSafe)
Toutes les réponses
mercredi 9 mai 2012 08:07Modérateur
As far as I know that SilverLight tools are compatible with VS2010 SP1. And to deal with your issue, please try to first re-install the VS2010 and then re-install VS2010 SP1 to see if it helps.
Vicky Song [MSFT]
MSDN Community Support | Feedback to us
mercredi 9 mai 2012 18:24
If you would look into the description of my problem and the steps we took to solve it, you would notice that we already tried to re-install VS 2010 and SP1. In fact, we did it several times. The error is still there and we are not able to use Version Control from within Visual Studio on the server which is supposed to be our production build machine.
Is it possible to open a direct ticket with Microsoft support and have someone to work with us on this issue?
mercredi 9 mai 2012 22:29
Can you please try applying the following patch on top of SP1 to see if that resolves the issue?
The method "OwnerNameMatches" was added in this patch, which makes me think that maybe you had it applied previously and then it was partially reverted by the Silverlight tools update. (Or I could be completely wrong about this sequence of events. But I would definitely try this update.)
- Marqué comme réponse Lana69 jeudi 10 mai 2012 18:06
jeudi 10 mai 2012 18:07
Thanks so much for your response - the installation of the patch has solved our issue.