Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Thanks for the reply, Well, now I am not sure if the problems was with the COM component, the atomic commits or some file conflicts. Either way it cleared up after I turned off the Atomic commits feature and did not return even when I turned atomic commits on again (just for debugging purposes). I'll do some more digging and extend the logging facilities on the component. I'll let you guys know what I find. Dan Pupek Software Engineer Advanced Systems Technology, Inc dpupek at astpcola.com <mailto:dpupek at astpcola.com> (850) 475-4038 -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Tony Hoyle Sent: Sunday, March 14, 2004 11:30 AM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: More COM extension problems Dan Pupek wrote: > The COM extension seems to hang after running a commit on any files that > have been removed . > That sounds like something to do with the extension itself, rather than the CVSNT server - we commit removed files frequently & have had no hanging problems (it would have been noticed rather quickly as we've recently been pruning large parts of the tree). Try writing debugging output (OutputDebugString and friends) as it's probably something simple. Tony _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs