windows - regular dll vs extension dll -


i have dll (a.dll) uses atl stuff, , can't have mfc in it. there stuff needs mfc though, made mfc regular dll, called b.dll , gets automatically loaded @ runtime a.dll (via import library).

the part of b.dll needs class (foo) defined in b.dll, , class has stuff in uses mfc. allowed create foo object in a.dll? b need extension dll instead?

the regular dll page says:

all memory allocations within regular dll should stay within dll; dll should not pass or receive calling executable of following:

  • pointers mfc objects

  • pointers memory allocated mfc

but extension dll page says

the client executable must mfc application compiled _afxdll defined., , a.dll can't mfc app.

is problem use regular dll in case?

thanks,

bryan

maybe i'm misunderstanding, if can't use mfc, , b provides class does, how can instantiate object in a? looking have b have factory function creates object , passes through pointer? in case need ensure b calls delete() on it, not a, because they'll have 2 different heaps.

is com object or mean 'import library'? talking 'regular' dll way stubs in .lib, or 'import library' .tlb? (not matters question think, i'm trying picture situation).


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -