Re: Determine if Regular DLL or Extension DLL

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 30 Jan 2008 16:15:24 GMT

Message-ID:

<wo1oj.1461$xq2.1312@newssvr21.news.prodigy.net>

"NEW2.NET" <NEW2NET@discussions.microsoft.com> wrote in message
news:630D1974-151E-47B4-A047-9C46F816FB25@microsoft.com...

We think we're having resource (e.g., dialog resources, menu resources)
collisions between the suspect DLL and the rest of the APP. A regular DLL
has its own resource environment and could not collide; an extension DLL
shares the resource environment with the MFC host app - if the resource
ID's
are the same, there can be collision problems.

Ah, OK. I took a brief look at the VC6 help file. (old but it's what I
had.) It said:

<quote>
Merging the resources and class names of all DLLs into the client
application's name space has the disadvantage that you have to be careful
what IDs or names you pick. You can of course disable this feature by not
exporting either your resources or a CDynLinkLibrary object to the client
application. TheDLLHUSK sample manages the shared resource name space by
using multiple header files. See Technical Note 35 for more tips on using
shared resource files.

</quote>

Maybe the DLLHUSK example sheds more light. I'm sorry, I've never used
extension DLL's.

Also, if you're stuck with the DLL you've got, you can just load it into
Visual Studio and view it's resources and see what ID's it's using. Then
alter your app to pick different ones.

-- David