Hi Jonathan,
In general I agree with you, I might add just a few comments...
>Looking to the future, I would guess that the SCC API will disappear in a
>future release, since MS has announced that in Visual Studio 7, DevStudio
>is disappearing and VC++ is being integrated into the same Visual Studio
>environment that hosts their other languages (VB, VI, VJ++). See
>http://www.microsoft.com/presspass/press/2000/Apr00/VCDCpr.asp. This would
>suggest that their direction is the SCC COM interface. What this does for
>third-party products that use SCC API is anyone's guess.
I would say that for quite a few years I see no problem here. My company is
still using VS5, and I don't see them to upgrade for looong time. I have
VC60 on my own. But if VS7 is going to look and behave like VB, then I will
not buy it for quite a looong time as well. I know many companies will still
continue to use VS5 and VS6 long after VS7 is out. Question of money and
habits :)
>Everything that needs the MS NDA is already complete and Preston did an
>excellent job of separating the two pieces and documenting the CoWorker
>interface between the pieces, so volunteers who want to work on the Open
>Souce part can simply write to Preston's CoWorker interface.
The last time I checked the sources and other downloads were pulled down...
>>2. To map SCC interface to CVS is not easy. SCC is more suitable for
>>reserved checkouts.
>
>I have spent much time scratching my head and asking how I should treat
>this awkwardness.
That is exactly why I go the different way. No Limits if you use Add-in!
>Finally, I find that WinCVS is such a good program, and it's so easy to use
>it as a separate process from DevStudio that most of the motivation for my
>continuing to work on the SCCAPI interface is merely pig-headedness and the
>sense that I will learn interesting things about COM from the project.
Now it is even esier to use WinCvs as a separate process :)
I initially made a GoToFile patch just for that purpose - to just call
WinCvs via the tool setup in the Tools menu of DevStudio so I don't have to
'hunt' for the files each time...
However with time it shown that it doesn't always do the right things for
you (try to put the caret into the output window and then use the tool with
the pathname as a paramenter...you get a call to: Output - Build.txt!!!???
). That is how CvsIn started to come to life... Now it is time to 'import'
all the cvs basic operation into CvsIn, and it is on the way... But still to
perform more complex operations, specially on the directories level, you
will use WinCvs.
>For people who want something soon, it's great that Jerzy produced an
>alternate solution that works on a much more limited problem domain, and
>only on one product, but which works today!
Thanks :)
It might be that generic solution via SCC is an overkill on Windows
platfrom. CVS has a good use and does excellent job in C/C++ / DevStudio,
but I would not be so sure about other languages/tools that use SCC
integration...
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
