Re: MFC DLL at Application Folder Saves Memory As Well?
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Wed, 28 Sep 2005 10:41:59 -0400
Cat <typingcat@xxxxxxxxx> wrote:
> If Not...
> I can delete the later one's own MFC71.dll. It still works fine as
> long as the MFC71.dll file exists in Windows\System32. In this case,
> do the two applications share memory and I can save memory?
Yes, in this case the two application share and save some physical
memory.
Be aware of the downside of this approach. Suppose the user installs
application A that drops the DLL into system32. She then installs an
unrelated application B, that checks whether the DLL is already present
and does not install its own copy in its local directory if it finds
that a copy already exists in system32. Both applications work fine, the
user is happy.
Some time later, she decides to uninstall application A. Being a good
citizen, A carefully removes all the files it has installed, including
the DLL in system32. Suddenly, a seemingly unrelated application B stops
working.
Search MSDN for the phrase "DLL Hell" to fully appreciate the issue.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- References:
- Prev by Date: Re: MFC DLL at Application Folder Saves Memory As Well?
- Next by Date: Re: DHCP Server Management API Functions
- Previous by thread: Re: MFC DLL at Application Folder Saves Memory As Well?
- Next by thread: RE: Operator new failing in windows after several days of operation
- Index(es):
Relevant Pages
|
