The gist of the matter is for programmers to avoid DLL Hell. MS
realised that the file did have many versions, so they
recommended to developers to distribute the version they wanted
and put it in the programs folder, NOT in a system folder. The
program will use the dll file in the program's folder, not the
one in the system folder. That is why the recommendation is
sound.
The way dll hell started is because programs would install the
version they wanted in the system folder, thereby breaking any
other program that did not use that particular version. If the
dll file is in the programs folder, it will not interfere with
other programs. So it is not a matter of having different
versions of the same file, but a matter of *where* that file is
located. The "files have to be the exact same version" you keep
saying as a mantra is what is outdated.
On Wed, 30 Aug 2006, Marc Sims wrote:
I've read the knowledge base article and I know that the file
in question MSVCR71.DLL as stated in my original post has
different versions. As I've acknowledged in that post its
hard to distinguish the diffrences between versions and even
the timestamp is of no help. Even If there are two different
versions of the same file MSVCR71.DLL that have a timestamp
of 7:01am and the other with diffrent timestamp of 7:01pm
with the same date there's no way accurately varify which is
the most current.
--
----------------------------------------
To unsubscribe, mailto: [EMAIL PROTECTED]
Is your picture included in the Official Win-Home List Members Profiles Page?
http://www.besteffort.com/winhome/Profiles.html
If not, write to: [EMAIL PROTECTED]
