>That's a fair question, and perhaps that is where I should start. I would like to implement a better source control system than the manual method we are currently using. I have spent a fair amount of time working with subversion, and while it can be made to work, it is fairly tricky to do conversion in and out of binary files.
>
>With TFS now available to us under our MSDN Pro subscription, I thought I would give it a try and see if it works any easier.
>
>So maybe I can bounce the question back at you. Why would I, or why wouldn't I want to use TFS with a combination of VFP and .NET projects?
>
>I had seen a post from you last year sometime indicating you were might be doing a write up on VFP with TFS, so I figured the idea must have some merit.
>
>>My understanding is there is supposed to be a new version of the COM-based source control API. If so, it should work.
>>
>>But just wondering...why use VFP with TFS?

TFS is a much nicer source control system than VSS for one thing. Simpe to set up, Internet enabled, a web client, and SQL based!

To use it with VFP you need the MSSCCI client for TFS which allows applications that have VSS clients to use TFS.

UPDATE: You'll need to search for the client - there was a beta 2 version available but I think they took the link down when TFS2010 released yesterday. I assume a release version of the MSSCCI client is forthcoming.