VFP, like VB6 and VSdotNet, uses Microsoft's Source Code Control API.
This is an API available from Microsoft only by signing an NDA, so
there are licensing issues with getting it to work with any Free tool.
I know that there is such an add-on for CVS, but I don't know how they
did that, legal-wise.
subVersion is much younger, so I don't know of an effort to integrate
it yet. A google search did bring up some interesting links, including
this post from Walter Nicholls of Cornerstone NZ:
http://www.contactor.se/~dast/svnusers/archive-2003-11/0040.shtml
Looks like there was a brief attempt in "Subway" at
http://nidaros.homedns.org/subway/, but it died at version 0.0.1
As for SourceSafe, no offense meant and none taken. I worked with it
for a decade and could get it to do what I wanted, inside of VFP and
inside a LAN, or with SourceOffSite. However, I spent a couple of years
trying to get the SourceSafe team to understand that they needed to
turn it into a well-documented component with separable front-end-UIs
and back-end ADODB interfaces, remote access, and so forth. It could
have rocked. They blew it. SourceSafe 2005 (hah!) will be too little,
too late, too proprietary.
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
On Oct 30, 2004, at 9:25 AM, Carl Karsten wrote:
> Thanks for the auto adding suggestions. It seems that even with some
> code, auto ADDing isn't exactly auto.
>
> So Plan B: use the VFP project to define what gets added. Vfp meny,
> Tools, Options, Projects, Source control options, Active Source
> Control Provider. Any idea how to get subversion to be a choice?
>
> Plan C: Project hooks. Anyone know where a project hook class is
> that does any sort of source control? even it it isn't subversion,
> seems like it would be a good place to start.
>
> I made a nifty util that will be cool if I can tie in:
> http://fox.wikis.com/wc.dll?Wiki~VcxDiff
>
> Carl K
>
[excessive quoting removed by server]
©2004 Ted Roche |
