will affect
multitudes of users of programs that use the IE7 webbrowser control. It
seems
that creating the control uses PSAPI.DLL, which is proliferated across
many
users' machines in many versions. The redistributable from MS is
version
4.0.1371.1. This version is INCOMPATIBLE with ieframe.dll, the new home
of
the webbrowser control. If this PSAPI is loaded, the dll cannot create
the
control, presumably because ieframe.dll is calling something in psapi
that is
not present in this version of the DLL.
The version present in XP SP2 is 5.1.2600.2180. This version IS
compatible
with the ie7 webbrowser control.
The problem: If a user's system loads the old version of PSAPI, it may
be
loaded because of some search-pathing kind of thing. In the case of our
app,
we were distributing the version 4.1371 in the same folder as our
executable,
because we were using other features of that library for which we
needed to ensure its presence (we have some NT4 users).
What MS needs to do: Either make ieframe.dll not fail on old psapi.dll,
or
allow redistributing of the 5.1.2600 or above version.
Shmuel Einstein
P.S. How do I tell someone at MS about this problem?
原贴: