Anybody has any idea why attempt to create a modal dialog in a C++ dll (regular or extension) fails in Premodal() when called fom a VB application It succeeds when called from C++ application.
Any help will greatly appreciated.
email for possible answer email@example.com
You've talk about prety much of it, but there's a holding issue:memory leaks. I've done a DLL whichs exports a bunch of functions, and one function makes an extensive use of manual memory(new and delete), and every time a execute that function from my client it makes an monumental memory leak, the function is correct because if it is pass to COM dll it works perfectally(as it should be) and I have no idea what going on...
Hi I like the article but agree with some of the confusions comments previously mensioned.
My problem as it stands is...
I am following your advice on connecting an Extension DLL to an application and both the DLL and application compile and link. The DLL interface is currently only 3 "C" functions exported to the application. The DLL is loaded with AfxLoadLibrary. My problem is the <myDLL>.lib file is included in the project->object/library modules entry in my eVC++ 3.0 environment I get an immediate "Cannot execute program" dialog when trying to run the applcation with the PPC emulator.
I have no other symptoms or information than this about the problem.
I take this <myDLL>.lib entry out then on linking there is the complaint about unresolved interface external functions as you'd expect. Take these away from the code and it runs without a problem.
Does anyone have an idea or have seen something like it before on any platform?
I am including an external library as part of the dll build and want to export the data items in this library through the dll. Do I use an extern with the declspec directive and what is the ___imp_ preceeding the data names from this library on a dumpbin? Do I need to dereference these items as pointers or just do an import in the application with an extern to use? HELP! Thanks.
Thanks for good sample...
but I got a problem.
No problem when DLL & EXE(Application) are both DEBUG mode
or RELEASE mode.
but, There is Assertion Error when DLL - DEBUG & EXE - RELEASE
or DLL - RELEASE & EXE - DEBUG...