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.
Tony Hoyle wrote: > Gerhard Fiedler wrote: >> I think that it would be a good idea to install a cvs.exe.local file with >> every cvsnt installation that installs any DLLs -- after all, using those > > No. It'll break stuff - possibly quite badly. Just don't install > multiple versions. In a way, this seems to say "Don't install TortoiseCVS"... Not sure that makes people happy :) It seems nobody has yet been able to explain what would get broken if a cvsnt installation that copied DLLs to its installation directory actually uses those DLLs. The only argument that I read so far was that some other tools rely on the registry entries so that they can find the proper DLLs. As long as these are there and point to valid DLLs, I don't see what could get broken if any other installation uses its own DLLs. My point, I guess, was: if DLLs get copied to the system, the purpose should be that they get used. If that is not the purpose, they shouldn't have been copied in the first place, no? Which kind of means that if you really want to enforce this, shouldn't the cvsnt installer look at the system and not install its own DLLs (or update the DLLs at the registered location) if they are already there? Not sure this would break fewer things, though... it quite possibly could break more. > Tortoise presumably tells cvsnt to use its own set of libraries anyway on > its default installs, so wouldn't have the issue. If you meant that Tortoise installs (or should install) a cvs.exe.local file with its default install (which it doesn't seem to do, at least not in the 1.9.12 install), then I come back to my suggestion: why not install this by default with every installation that installs the relevant DLLs in its own directory? If you meant something else: How would Tortoise tell cvsnt to use its own set of libraries? It apparently didn't do that (at least not in the 1.9.12 install), and it doesn't look like the developers know how to do that -- they referred to the cvs.exe.local workaround. (Which seems to work, hence my suggestion.) > Or use simcvs which is designed for that use. Is simcvs.exe independent of the exact version of the installed cvs.exe? If not, how could Tortoise install the correct simcvs.exe? Gerhard