[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DLL hell with Latest Tortoise Release Version

From: Jody Shumaker <jody.shumaker_at_gmail.com>
Date: 2006-02-07 03:18:47 CET

Any particular reason you're still using the beta version? Not sure when
they were released, but my best guess is that you have some stuff built
against your beta version, that isn't compatible with the final release
version. Also if you had this installed from Windows 2005 beta, I believe
there's issues with it not uninstalling everything properly.


- Jody

On 2/6/06, Luke Hudson <lingo@paradise.net.nz> wrote:
> Hi there. I have used TortoiseSVN for a while - it's great!
> Unfortunately, I've found a problem on my machine with the 1.3.1 release.
> After installing it, TortoiseSVN works fine, but many other programs do
> not. The particular problem is msvcr80.dll, which is installed into the
> %WINDIR%\system32 directory by Tortoise's installer. After install,
> many programs report that the entry point _encode_pointer cannot be
> found in this dll.
> Presumably, it's a dll version problem, and may be something to do with
> the DLL search path on my machine. However, everything works fine until
> I install 1.3.1, and the problem can be fixed by using the old version.
> I'm running Win2000 Professional, with the .NET Framework 2.0 Beta
> installed. Before install, I found msvcr80.dll installed in the dir:
> "C:\WINNT\Microsoft.NET\Framework\v2.0.40607"
> I'd certainly love to use the new version - can anyone tell me what's
> going on here?
> I hope this report is useful to someone; keep up the great work
> developing!
> Thanks,
> - Luke
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Feb 7 03:18:53 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.