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.
McNamee, John wrote: > s/cvs.exe/cvs apis/ and the same question still applies. cvsapi.dll > and/or cvstools.dll can easily find out where they live > (GetModuleFileName with the HINSTANCE passed to DllMain), and load the > protocol DLL's from there. Is there a case where you'd want the > cvsapi/cvstools DLL's in one directory and the protocol DLL's in > another? I'm still not seeing why a registry lookup is needed. > In 2.6 (maybe even 2.5.04 if that goes ahead) that's exactly what will happen - the current layout on Windows is too messy to continue much longer and doesn't scale. It needs to be more like Unix, where there's clear separation. How does a 3rd party install find cvsapi? It looks in the registry. The same applies - you can't have two of them. COM objects talking back to cvsapi? Same. The fact remains that trying to install two different versions has *never* been guaranteed to work, except in the limited case of a self contained client frontend (eg. MacCvsX which uses this to stay in a single directory). Tony