Arne Moor wrote:
> with 1.3.1 it doesn't let you start the setup, thanks that you changed
> the setup to check for admin privileges. But there is a solution to
> deploy without admin-rights!
>
> As in our company by policy per machine installations are only allowed
> by engineering, for which I guess it will take some additional months to
> deploy the Vs2005 runtime, i searched a little bit....
>
> What I found is interesting in that it's not a MS must to install them
> as side-by-side assemblies. In the MSDN library at
> http://msdn2.microsoft.com/en-us/library/ms235317(en-US,VS.80).aspx
> under "Procedures for deploying Visual C++ library DLLs as private
> assemblies" they describe that it's Ok to deploy the CRT and MFC as
> private assemblies.
>
> As MS describes at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sbscs/setup/assembly_searching_sequence.asp
>
> it's even no conflict or problem with updates, since as soon as the CRT
> and MFC are deployed as side by side assemblies into %windir%\WinSxS
> those are allways used over the private ones.
>
> A proposal to make all the user (inside biger companies) happy:
>
> - Leave the current check for MFC inside WinSxS as it is.
> - If not installed copy the following from VS2005 to TortoiseSVN\bin:
> \VC\redist\x86\Microsoft.VC80.CRT
> \VC\redist\x86\Microsoft.VC80.MFC
> \VC\redist\x86\Microsoft.VC80.MFCLOC
> - remove the MSMs from the setup.
> - Let also none-admins start the setup.
>
> I tried this today, installed TSVN 1.3.1, removed temporary all MFC &
> CRT stuff and copied those three folders into TortoiseSVN\bin.
> Dependency Walker showed that they where successful used. Afterwards I
> re-enabled the original WinSxS stuff and after a reboot those files
> where used instead of the private assemblies.
>
> Any comments?
Played a little with the WiX scripts:
* installed the MFC/CRT dll's directly into the TSVN\bin folder
=> works on Win2k
=> doesn't work on a fresh XP SP2 machine
* installed the MFC/CRT dll's into assembly subfolders
Microsoft.VC80.CRT, Microsoft.VC80.MFC and Microsoft.VC80.MFCLOC
=> works on XP SP2
=> doesn't work on Win2k
* copied the dll's from the subfolders back into the bin folder
=> works on Win2k
=> works on XP SP2
You see now, it's not that easy. It won't work on either Win2k or XP,
depending on where/how we install those dll's. Why it works when the
dll's get copied from the assembly subfolders to the bin folder but not
when directly installed in the bin folder on XPSP2 I don't really know.
I guess the OS keeps track of those dll's and remembers that it has
already verified them as the correct assemblies.
If I find a way to make the msi install the files depending on OS
version to a different location (without having those dll's twice in the
msi), I may change the msi for the 1.4.x version.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Mar 10 23:36:00 2006