Finally i have been able to update from our slightly modified CC.Net 1.4 to 1.5 and i didn't see any problems so far. The change to the XML API seems to work very well.
When i log into the server i sometimes see a messagebox from the MKS client saying that a connection was terminated because of an already running one or something, but this does not seem to have any impact on how CC.Net works. I have seen hanging IntegrityClient processes in a few situations, but not CC.Net or Windows related. On one of our linux boxes the command line did not want to connect and then left about 10 dead processes. IIRC it was a configuration issue... I'm looking forward to add more MKS projects to our CC.Net setup soon. If i run into any issues i will let you know. regards, Daniel "Dave Johnson" <[email protected]> wrote: > I just wanted to shoot a message out to the CCNet users who use MKS > Source. How has your experience been? > > Overall, I've been working just fine after some recent updates to the > trunk. > > One thing I run into is, after a week or so of uptime, eventually the > MKS source client fails the checking source phase. Then you either > have to log onto the server and kill IntegrityClient.exe processes > (sometimes more than one) or just reboot if you like more grand > solutions. > > Thanks. > Dave Johnson
