Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
msm for mfc42.dll
1 view
Skip to first unread message
samuel eisenpress
Aug 22, 2003, 2:11:18 AM8/22/03
to
I must be missing something here. I've made an
installation using the merge module for mfc42.dll. But I
understand it's recommended that I install mfc42.dll to
the directory where my executable is installed, in case
there are multiple version of the dll on the target
system. In fact this seems necessary, considering error
messages that the application is giving (it seems to be
using an older version of the dll and not finding a
function it needs). But the msm uses a key path, not a
file, as a key; so if the merge module has been installed
before but to a different directoy, it won't install. It
would seem the only solution is to forget about the merge
module and add mfc42.dll directly to my installation as a
component. What good is the mfc42.dll merge module?
What is the recommended method if installing mfc42.dll?
installation using the merge module for mfc42.dll. But I
understand it's recommended that I install mfc42.dll to
the directory where my executable is installed, in case
there are multiple version of the dll on the target
system. In fact this seems necessary, considering error
messages that the application is giving (it seems to be
using an older version of the dll and not finding a
function it needs). But the msm uses a key path, not a
file, as a key; so if the merge module has been installed
before but to a different directoy, it won't install. It
would seem the only solution is to forget about the merge
module and add mfc42.dll directly to my installation as a
component. What good is the mfc42.dll merge module?
What is the recommended method if installing mfc42.dll?
Kallely Sajan
Aug 22, 2003, 11:39:07 AM8/22/03
to
Which mfc version are you referring to.
--
--
Regards,
Sajan.
PS: Please don't send me direct emails, use the newsroom.
"samuel eisenpress" <s...@cad-design.com> wrote in message
news:06e001c36874$33ab1150$a601...@phx.gbl...
Phil Wilson
Aug 22, 2003, 1:30:47 PM8/22/03
to
I've never seen a recommendation that mfc42.dll be installed to the application
folder. The right place is really the system directory, basically because it's a
COM DLL (there are classes in the merge module).
--
Phil Wilson [MVP Windows Installer]
----
"samuel eisenpress" <s...@cad-design.com> wrote in message
news:06e001c36874$33ab1150$a601...@phx.gbl...
folder. The right place is really the system directory, basically because it's a
COM DLL (there are classes in the merge module).
--
Phil Wilson [MVP Windows Installer]
----
"samuel eisenpress" <s...@cad-design.com> wrote in message
news:06e001c36874$33ab1150$a601...@phx.gbl...
samuel eisenpress
Aug 23, 2003, 1:50:10 AM8/23/03
to
I searched my computer and found 17 copies of mfc42.dll.
These were all installed by commercial applications from
major companies (none installed directly by me). I
searched the C++ documentation and didn't find a specific
recommendation to install mfc42.dll in the application's
directoy, except in the case of an mfc42.dll which has
been modified and rebuilt.
These were all installed by commercial applications from
major companies (none installed directly by me). I
searched the C++ documentation and didn't find a specific
recommendation to install mfc42.dll in the application's
directoy, except in the case of an mfc42.dll which has
been modified and rebuilt.
If the mfc42.dll currently in the system directory is an
older version than the one in the merge module, will it
be updated?
>.
>
samuel eisenpress
Aug 23, 2003, 1:51:45 AM8/23/03
to
I need to install mfc for use by C++ 6.0.
-Sam
>.
>
Phil Wilson
Aug 23, 2003, 6:16:18 PM8/23/03
to
I'm pretty sure that the COM objects in mfc[u]42.dll are so obscure or old
that nobody ever uses them, so these applications can get away with
installing it to their own application folder but not registering the DLL.
So the right answer is that if you self-register it (or use the merge module
with its entries in the Class table) you should install it to the system
directory, otherwise the application folder works fine.
that nobody ever uses them, so these applications can get away with
installing it to their own application folder but not registering the DLL.
So the right answer is that if you self-register it (or use the merge module
with its entries in the Class table) you should install it to the system
directory, otherwise the application folder works fine.
Yes, it will be updated.
--
Phil Wilson [MVP Windows Installer]
"samuel eisenpress" <s...@cad-design.com> wrote in message
news:062501c3693a$69c5b490$a401...@phx.gbl...
0 new messages