index > Team Foundation Server - Version Control > MSSCCI Provider and SQL Management Studio

MSSCCI Provider and SQL Management Studio


I have just installed the lastest MSSCCI Provider with hopes to use it with SQL Management Studio 2005. The install seam to go fine. I have set "Team Foundation Server MSSCCI Provider" as the source control plug-in. I can see the File->Source Control menu which has two options:
1. Open From Source Control
2. Launch Team Foundation Server MSSCCI Provider
One issue and one question.
If I choose "Open From Source Control" I get a dialog for connecting to TFS. My TFS server is properly defined but when I press OK to connect I get the follow error dialog box. It states: Microsoft.TeamFoundation.Client.TeamFoundationServer..ctor(System.String, System.Net.ICredentials) the only option is to press OK but nothing happen after that.
What is the purpose of "Launch Team Foundation Server MSSCCI Provider"? When I select this it launches a new copy of Visual Studio 2005. Even after launching VS the issue I described above still exists.
Addtional Info:
I have been successfully using VS2005, Team Foundation Explorer and TFS for months.
Scott



ScottPGlover
ScottPGlover

Hello,

The error you are getting looks like mismatch between the apis' version of tfs OM. Two questions arise:

  • do you have RTM version of Team Explorer on your box? The error you are getting happened quite often when using Msscci against Beta3. Have you used beta3 and then upgraded to RTM, or have you installed RTM from the beginning?
  • just for the sake of sanity please check if your Msscci Provider is 1.1 (readme.txt in the install directory)

"Launch Team Foundation Server MSSCCI Provider" is a Msscci way to bring up external client tool, in case of TFS it is Team explorer or Visual Studio 2005.

Thanks




Michal Malecki
Michal Malecki
Michal,
Thanks for the reply.
First I just want to clarify what you mean by "apis' version of tfs OM"? Specifically what is "OM"?
I do have the 1.1 release of the MSSCCI Provider as determined by looking at the Readme file.
I did previously have Beta releases of Visual Studio and possibly Team Explorer on my workstation. I know there were many issues with the beta releases and that you had to be very careful to fully remove them before installing the production releases.
How do you determine the version of Team Explorer? If I look at the entry in "Add or Remove Programs" it is listed as "Microsoft Visual Studio Team Explorer - ENU". If I look at the "About Microsoft Visual Studio" information it states that I have VS 2005 Version 8.0.50727.42 (RTM.050727-4200) and that Team Explorer is one of the installed products.
I thought I was running all of the lastest production releases of VS and Team Explorer; would the above information lead you to believe otherwise?
Scott



ScottPGlover
ScottPGlover

Hello,

I'm sorry that I have written it in such a confusing way. What I wanted to say is that the error can be caused by the difference in the constructor signature between TeamFoundationServer class which the Msscci was built against (the RTM) and the one that is loaded when you start the Msscci provider.

Please go to "About Microsoft Visual Studio" dialog, select Visual Studio 2005 Team Explorer, in the Product deails you should see version of the Team Explorer. What is it?

Next please, go to GAC using the command prompt (or file manager different the Windofile ws Explorer) - "cd /d c:\WINDOWS\assembly\GAC_32\Microsoft.TeamFoundation.Client\8.0.0.0__b03f5f7f11d50a3a" and check size of the Microsoft.TeamFoundation.Client.dll - I'm pretty sure on RTM it was 163.840 B




Michal Malecki
Michal Malecki - MSFT
reply 4

You can use google to search for other answers

 

More Articles

distributed development environment
Cannot create new build type on TFS client machine
Subfolder overwrite issue in Team System RTM
Reporting against TfsVersionControl
Error TF60024
Bug: Merging VS Solutions / Projects
TFS MSSCCI Provider
Exporting files with check in date
Build checks out and locks local project output dlls?
Source Control Reporting
Welcome to Bokebb   New Update   Joins the collection  
 

New Articles

Using Visual Studio 2005 Source Control
Check In Comment
How to "perminately" delete a …
Logging files modifications
Developer has no access to SCC
No appropriate mapping exists for $/Proj…
Deny delete permissions on source control
Branching
New Team Foundation Server MSSCCI Provid…
BizTalk 2006 and Team Foundation Server …
One big team project, or Eight small ones?
Is this Is right Way to Share Code in TF
How to search TFS comments from Visual S…
Why does TFS's Version Control employ fo…
PendDelete usage and differences between…

Hot Articles

Strange Rollback / Get Specific Version …
Compare directories
RE: Checkin a project into VSS 2005
Copy source control items with history
TFS MSSCCI Provider Final fails to install
The underlying connection was closed
Should we normally check Source Control …
Shelving
Massive confusion here...
Why does TFS's Version Control employ fo…
TF10139: problem after upgrade freom B3R…
Re: Visual studio locking up when doing …
Programming against MSSCCI provider
Getting latest version...
Is using workspace.Get() right?

Recommend Articles

Any exiting tools or method to print out…
Custom check-in policy
Web Services Projects not under source c…
Project files of our solution are automa…
Problem with Automatically added Locks
MSFS - Supporting non Microsoft developm…
ThreeWayMerge.Run() crashes when IsBasel…
merge /discard command problem
Delete label by Id, TFS API
vssconverter error TF60702
Lock Up Issuses w/ Source Control Explorer
VS 2005 Solution Explorer's Getlatest no…
Merge by WI
TFSVC API - Workspace.Get and GetOptions…
Check-in from different directory