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

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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@xxxxxxxxx> wrote in message news:1177646826.588726.248520@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Apr 26, 12:10 pm, rgs424 <rgs...@xxxxxxxxxxxxxxxxxxxxxxxxx> 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


.

Relevant Pages

  • Re: Error loadin VS 2005 DLLs in Windows Vista
    ... The scenario is a Legacy VC 6.0 application which we are adding new mixed ... mode DLLs compiled with VS 2005. ... Installing the Visual C++ 2005 Redistributable changes the error to: ... Have you tried a "Thinstall Solution"? ...
    (microsoft.public.vc.language)
  • Application failed to initialize 0xc0000022 - Access rights to System32 DLLs
    ... I had EXACTLY the same issue on our Win2k Citrix farm after installing ... We found that the ICA clients got this error ... are running fine if the user has Admin rights but if not, ... Those DLLs do not allow ANY access to ordinary ...
    (microsoft.public.vb.general.discussion)
  • Re: directx redistribution
    ... and tried installing it on another machine. ... If you were referanceing the dlls in the project directory you ... > I would remove the referances to the MDX files and re add them making sure ... >> including a copy of the direct3d dlls in the target folder. ...
    (microsoft.public.win32.programmer.directx.managed)
  • Re: What Linux can learn from Windows...
    ... >> one false bit in the registry and the pc won't boot anymore. ... I had a registry get messed up by installing a NIC into a Windoze machine. ... The biggest problem with Windoze is the .DLLs and where they get installed. ...
    (alt.os.linux)
  • Re: location of MFC71*.dlls when installing a program ?
    ... as my .EXE, instead of installing them in WINNT/SYSTEM32? ... MSFT does not recommend touching sys32 with your libraries. ... Also, when you are installing it local, chances of it being deleted by ...
    (microsoft.public.vc.mfc)