New Team Foundation Server MSSCCI Provider Available Now!
I am happy to report we have released an updated TFS MSSCCI providerhere. We have been able to address a number of requests (keep them coming) in this release including the following:
- PowerBuilder support
- Enterprise Architect support
- Improved Open from SCC experience
- Work items can now be modified in the checkinwindow
- Get latest on checkout support
- Check-in lock is treated as exclusive
- Setup works on x64
This is an unsupported "powertoy" like tool. There have been some discussions about the possibility of supporting it, but nothing yet. Keep reporting issues and comments to theforumor bye-mail.
[1270 byte] By [
EdHintz] at [2007-12-21]
Has there been any decision made on whether this will be supported or not? I heard rumours that it was now supported by PSS?
The TFS MSSCCI provider is not currently supported. Howver, we have heard the requests to support the MSSCCI provider and we are actively working on that. There are many steps involved in preparing the support organization and getting everything in place. Stay tuned.
Ed
http://blogs.msdn.com/edhintz
Now that we can link from SQL Mgmt Studio with the wonderful MSSCCI provider, is there a way to setup the TFS Version Control to auto open SQL Mgmt Studio when you double click on a .ssmssln like it opens Visio when you click on a .vsd?
I have installed this thing in the hope of using it to manage my VS.NET 2003 projects with CodePlex and now I cannot check in locally or use my local VSS.
Is there any option or I simply have to uninstalled it?
I am getting frustrated with these so-called Microsoft innovations.
I am using the quest sql navigator.
so, can I use that with this MSSCCI provider?
thanks
Hi,
Yes.
1. uninstall MSSCCI from Add-remove programs.
2. reinstall VSS6.0d or VSS8
and everthing work fine. At least on my PC. I had same situation as you. But the resolution is very simply and obvious.
No question that the two source controll programs VSS6.0d/8 and MSSCCI do not like each other in VS2003 now. This is where MS should improve a little on them. :) I hope it will work soon becaue we currently migrate projects and there are many of then written in VS2003. This product has been released but we want to publish point release 1 soon and we would like to use Team Foundation Server, but we don't want to change VS2005. We are using VS2005 in the next major version, and Team Explorer works fine in a test environment.
So the scenario is: VS2003 and Team Foundation Server and some times VSS6.0d :). It is not a perfect constellation yet.
Proxymo: you don't need to uninstall anything. Use this: http://alinconstantin.homeip.net/webdocs/scc/VSS_Internet.htm
Thank you for the information, it is very useful. I think we have a little bit different problem. We would like to use Team Foundation Server source control and VSS from different VS2003 projects. This is not clear for me yet that how we should do it, but when I install MSSCCI Provider, VS2003 is not able to use legacy VSS databases. Using VSS is necessary because there are projects in VSS and there will be projects in TFS using VS2003 in both cases. I know we should switch to VS2005 and we did it in main stream codebase, but we have to support previous releases written in VS2203.
So I play with this situation in a test environment but I experimented that after MSSCCI Provider installed, VS2003 does not work with VSS. I tried to change the provider when change "VSS" SLN to "TFS" SLN, but without any effect. VS2003 always want to connect to TFS. It is not impossible that I did something wrong way. :) I did not give up! (TFS would be better solution because our team became bigger (50) during last 4-5 years and TFS not only a SourceControl tool.)
Hello,
VS2003 is always using the default Msscci provider. You need to change it every time you want to start working on solution that has different provider. Please look at my blog post
Are you guys planning on support of Intellij IDEA?
We haven't tested Tfs Msscci with this Ide. I hope we can do this in one of the future releases (the earliest release will support TOAD)
Hi,
You suggestion works well, thanks! When I modify (change back) regkey, old SLNs in VS2003 work!
I converted our VS2003 SLN and VCPROJ files of the project what we would like to control using TFS. SLN and VSPROJ contain references to TFS cource control. It looks work well. :)
A little attention is needed when I have to work with old-old projects that are using SourceSafe. Before using them, I have to change RegKey. When I switch to FTS project I have to change back. (Using two different SLN in same time is not possible on one PC.)
Thank you!
