Re: C++ Version 6 app using c++ version 8 dll

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 12 Apr 2007 21:22:12 -0700

Message-ID:

<96C09734-1652-4742-BCC6-D9A25C8E980A@microsoft.com>

I typically get some message about the application not loading properly (I
don't remember it verbatim). It's a non-descript message. If it said
something like "The new SP1 update made it so you have to recompile
everything you ever used so anything will work like it did right before you
loaded the update" then I wouldn't have had to spend an hour trying to
figure out what had happened.

:o)

Tom

"Norman Diamond" <ndiamond@community.nospam> wrote in message
news:ObOuF6XfHHA.5044@TK2MSFTNGP05.phx.gbl...

"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:BBCTh.16403$Um6.3538@newssvr12.news.prodigy.net...

"Norman Diamond" <ndiamond@community.nospam> wrote in message
news:ea09CJWfHHA.5056@TK2MSFTNGP02.phx.gbl...

[Attribution stolen:]

I thought the whole SxS scenario fully supported some modules (exe or
dlls) in a process could be non-SP1, and some could be SP1. Both the
non-SP1 and the SP1 RTL and MFC DLL's would be loaded into the process
as needed?

Exactly the opposite happens. As far as I can tell, a program compiled
by non-SP1 can probably load the SP1 MFC and CRT, but that's all. A
program partly compiled by non-SP1 and partly compiled by SP1 tries to
load both, and then the loader never proceeds far enough to see if just
the SP1 version would be adequate, it just detects the conflicting
compiled dependencies.

It detects the conflict and then does what exactly?

Aborts.

Does the process have both SP1 and RTM versions of the CRT/MFC or not?

Neither. The process dies when the loader aborts.