Re: vcredist question (slightly off topic)
"Goran" <goran.pusic@gmail.com> wrote in message
news:0d3c1f29-758d-491a-a57c-010fd70b775f@w6g2000yqw.googlegroups.com...
On Aug 4, 8:42 pm, "David Ching" <d...@remove-this.dcsoft.com> wrote:
Use SxSTrace.exe to find out. Probably a third party library you are
linking to was built with SP1 and that is why your .exe depends on it.
No, no, my executables DLL depends on MSVCR90.dll, MSVCP90.dll and
MFC90.dll, and the version of these don't match. Thanks for the tip
about SxSTrace (good thing one is old, one learns a new thing every
day ;-) ).
The default behavior is that when your .exe is linked, the linker scans any
..obj/.lib you are linking with for /manifestdependency or equivalent, and
any dependencies found there are PUT INTO YOUR EXE's MANIFEST. So your .exe
manifest will be a merge of a) what your .exe requires, and b) what the libs
your .exe links to require. I suggest it is b) that is causing the "wrong"
version to be put into your exe's manifest.
SxSTrace really is good. Did it show you which DLL's were preventing your
exe from loading --- no activation context successfully created?
-- David