On 12/16/05, Stefan Küng <tortoisesvn@gmail.com> wrote:
[snip]
>
> *if* you install those dll's as private side-by-side assemblies. You
> can't just copy them in your installation folder as you did with the
> CRT71 dll's. You must create the same directory structure as you find in
> %WINDOWS%\WinSxS\ - including the directory names and the manifest files
> beside the CRT dlls.
> Those dll's are compiled as side-by-side assemblies and refuse to be
> loaded 'the normal way'. At least on XP. On older OS which don't even
> know about side-by-side assemblies, you can of course install them as
> you did the older CRT dll's.
>
> Since installing side-by-side assemblies is not that easy (even if you
> install them as private sbs assemblies in your install folder), MS
> provides msi merge modules which handle the installation of these dll's
> for you. You can find them in %PROGRAMFILES%\common files\merge modules.
After getting annoyed with this situation enough that I started
searching around and pestering MS, it turns out you just need to copy
the .manifest file along with the runtime dll's (located in
C:\VS2005\VC\redist\x86\Microsoft.VC80.CRT) -- I've tried it by
copying svn.exe + support dlls + c runtime dlls (and manifest) + to a
new folder on a fresh XP machine and it is working fine.
So, it's actually very easy to install the C runtime dll's into your
app's private folder -- just make sure you copy the dll's manifest
file as well as the dll files themselves.
Just wanted to clear this up since it seemed so unbelievable to me.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 2 03:41:16 2006