On Thu, Aug 20, 2009 at 1:51 PM, Mike Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Thu, Aug 6, 2009 at 3:12 PM, Marcus D. Hanwell<<a href="mailto:marcus@cryos.org">marcus@cryos.org</a>> wrote:<br>
> James Bigler wrote:<br>
>> On Thu, Aug 6, 2009 at 12:10 PM, Bill Hoffman<br>
>> <<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a> <mailto:<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>>> wrote:<br>
>><br>
>> James Bigler wrote:<br>
>><br>
>><br>
>> Well, I was using VS 2005 64 bit with SP 1. I wonder if there<br>
>> is a similar bug or if there is something else going wrong<br>
>> such as what Marcus Hanwall described.<br>
>><br>
>><br>
>> I am not sure what your issue is, but I know I have done this many<br>
>> times...<br>
>><br>
>> -Bill<br>
>><br>
>><br>
>> I checked the version numbers of the DLLs, and even checked the md5sum<br>
>> and everything was the same between the dlls in the WinSxS folder and<br>
>> the ones I'm distributing. It failed on two clean systems without the<br>
>> vcredist install. I guess I'll run vcredist as Microsoft suggests and<br>
>> see if I can trouble shoot later.<br>
>><br>
>> It is a rather perplexing problem.<br>
>><br>
> The link Bill supplied has all of the relevant information. In the<br>
> "Community Discussion" section the second comment provides three<br>
> possible workarounds. We are using the third of those when distributing<br>
> Avogadro packages for Windows. The version mismatch in the manifests of<br>
> the compiled executables and the manifest with the redistributable DLLs<br>
> is what causes the issue.<br>
><br>
> It seems that MS has no intention of fixing this issue. We have a clean<br>
> VM where we test new installers, as occasionally this change was lost<br>
> and the DLLs failed to load.<br>
><br>
> Marcus<br>
<br>
</div></div>Ok, so I too have run into this problem. What is anyone doing to get<br>
around this issue?<br>
<br>
I would really like a solution that did NOT involve editing anything<br>
from VC++ install as I would have to pass those instructions on to the<br>
next Developer. Clinton's posting about including the VCRedist.exe in<br>
the NSIS installer is OK by me. Is that what everyone else is doing?<br>
<br>
Thanks<br>
--<br>
<font color="#888888">Mike Jackson<br>
</font></blockquote></div><br>I ended up linking against the static CRT library (/MT), but that's not for everyone.<br><a href="http://msdn.microsoft.com/en-us/library/ms235460.aspx">http://msdn.microsoft.com/en-us/library/ms235460.aspx</a><br>
<br>My next choice was going to be including the VCRedist.exe in the installer. For some of the other projects at my company, this is what they do.<br><br>Here are some links I've been consulting on the subject of CRT library (conflicts with multiple CRTs).<br>
<a href="http://stackoverflow.com/questions/1075050/howto-multiple-versions-of-msvcrt9-as-private-sxs-assemblies">http://stackoverflow.com/questions/1075050/howto-multiple-versions-of-msvcrt9-as-private-sxs-assemblies</a><br>
<a href="http://tedwvc.wordpress.com/2009/08/10/avoiding-problems-with-vc2005-sp1-security-update-kb971090/">http://tedwvc.wordpress.com/2009/08/10/avoiding-problems-with-vc2005-sp1-security-update-kb971090/</a><br><a href="http://stackoverflow.com/questions/1265792/visual-studio-2005-security-updates-and-crt-dll-versions-in-manifest">http://stackoverflow.com/questions/1265792/visual-studio-2005-security-updates-and-crt-dll-versions-in-manifest</a><br>
<br>James<br>