Geek asks and answers

Recompiling MFC Extension DLL Changes Entry Points of Exported Functions

I have a MFC Extension DLL that exports a C ++ class, and I need to change the behavior of the class method. Changes do not affect the signature of class methods.

I do not want to recompile modules that used the "lib" file of a previously released version of this library.

What happens if changes change the address of entry points for functions?

For example, the constructor address has changed:

Export   Ordinal      Function    Hint                      Entry Point
[+  ]    3 (0x0003)   2 (0x0002)  ??0CLangManager@@QAE@XZ   0x00009CB0    (OLD DLL)
[+  ]    3 (0x0003)   2 (0x0002)  ??0CLangManager@@QAE@XZ   0x00009760    (NEW DLL)

Should I recompile modules that use the library?

I tested the recompiled library - with new entry points - using the released executables, and everything works fine. I'm not sure this scenario hides some side effects.

When is it necessary to recompile the executable file associated with the DLL?

?

+5
1

DLL - , , , . , .

, , DLL, , .

. - DLL.

: , , , . , DLL, , new. , DLL . , PIMPL .

+2

More articles:


All Articles