Re: location of MFC71*.dlls when installing a program ?

From:

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

Newsgroups:

microsoft.public.vc.mfc

Date:

Fri, 27 Apr 2007 07:19:07 -0700

Message-ID:

<650351AB-7522-496E-809B-B49CD605288C@microsoft.com>

I also agree with this one. A local copy of the MFC DLLs doesn't take up
too much room and you are always assured that your program will have the
DLLs you intended to run it with. If you rely on the installed "system"
version you may find your program not working at some point when someone
installs a different version with the same name (I've had this happen).

Tom

"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:1177646826.588726.248520@n15g2000prd.googlegroups.com...

On Apr 26, 12:10 pm, rgs424 <rgs...@discussions.microsoft.com> wrote:

My program consists of only a single .EXE, with dependencies on
MFC71*.dlls.
Isn't it correct that I should install the MFC71*.dlls in the SAME
directory
as my .EXE, instead of installing them in WINNT/SYSTEM32 ? I believe I
read
that this is the 'common practice'.

If this is correct, then why ?

Thanks so much !!

Having a local copy is a better solution than copying it in Sys32.
MSFT does not recommend touching sys32 with your libraries. In
addition, you may overwrite an existing DLL which may be a custom one.
Also, when you are installing it local, chances of it being deleted by
some other app during its uninstallation are almost negligible.

---
Ajay