Export Redirecting w/ Mangling

Hot Topic

problem using CString::Format
How do you develop an interface for an existing C++ program?
another hook question
Why does adding a MessageBox make so much difference?
Do I need Visual C ++ Express Ed. Beta 2???
How do I get the PDB source file checksums with DIA?
udp sockets without using MFC
Why AfxGetResourceHandle causes Asserts?
XML Documentation Comments
Benefits of porting a VC++ 7.1 app to VC++ 2005

Visual C++

Error when trying to run apps on other computers
VC8 preprocessor problem
windows.h not found...
error C3867: 'A::test': function call missing argument list; use '&A::test' to create a pointer to member
What do I do!
CG and Visual Studio 2005
build error
excpt.h error
AddPrinterConnection returns 2
Meaning of DataSet header file icon

Export Redirecting w/ Mangling

Hi,

I'm redirecting exported functions in my library to existing libraries on my system in my .def files. Any guidance/best practice in redirecting mangled-name exports or should I just continue using the below

Example:
RegCloseKey=COMCTL32.RegCloseKey
RegEnumKeyExW=COMCTL32.RegEnumKeyExW
2@YAPAXI@Z=MSVCRT. 2@YAPAXI@Z

Thanks,
Rafael

Answer this question

Export Redirecting w/ Mangling

  • Richard Polunsky

    I sincerely suggest that you find a means of Debugging your export program Heirarchically with or in compatibility with the new CLR - v2.0, taking care and making sure that your Libraries are all compatible (or vice versa) especially with ADO.NET, COM+ and the DOM. I would be sure that they are also compatible with XPATH if necessary. 'Hope this helps.

  • Export Redirecting w/ Mangling
Answer this question