New source control API in Visual Studio 2005

dvdtknsn · Post by **dvdtknsn** » Wed May 30, 2007 2:03 pm

http://www.ericsink.com/scm/scm_ide_integration.html

In Eric Sink's pages it says:

"...We are currently working on an Eclipse plugin as well as a completely new plugin for the new source control API in Visual Studio 2005. Sometime in early 2007, we will be ready to consider our IDE clients to be primary"

Is there a plugin that uses the new source control API yet? Or does it still use the SCCI?

Thanks,

David

lbauer · Post by **lbauer** » Wed May 30, 2007 2:39 pm

Vault 4.0 and Fortress 1.0 both due to be released next week, will support Eclipse, plus the new VSIP integration with VS 2005.

dvdtknsn · Post by **dvdtknsn** » Wed May 30, 2007 3:39 pm

Thanks for the quick response.

If a tool should be integrated with source control tools like yours, there are a number of options available:

1) use the tool's native API
2) use SCCI
3) use this new VSIP VS2005 integration (is this its official name?)

(1) isn't ideal - it may be the most flexible, but would only work for one tool. (2) is known to be hard to implement and has its limitations, but many source control tools support this. (3) is new(ish), and possibly not widely supported. Vault 4 may have this, but do other vendors support it?

Does anyone have any recommendation on this issue?

Thanks,

David

lbauer · Post by **lbauer** » Thu May 31, 2007 6:01 am

I'm not a developer, but based on the support issues I've seen, there doesn't seem to be one type of interface that works universally with any kind of source control system.

You probably need to look at your product, and your market and determine which integration would be best for them.

For instance, there are many development tools that use MSSCCI, but that doesn't automatically make them work with Vault, even though Vault supports MSSCCI. The way the integration is implemented varies by product, so we have to thoroughly test and make changes to Vault to specifically work with the various versions of Visual Studio. That will probably be the case with the new VSIP integration as well.