Export functions in an exe
-
__Stephane Rodriguez__ wrote: ¿De qué se ríe un tonto? De ver reír a otro tonto. Can someone translate this to English? Did you just call me an idiot? Darroll Not one person lives in the present. Only the past. I can prove it.
Ok, too bad you don't guess it. I am saying the discussion you and Rickard are having is making my day. Thanks a lot.
She's so dirty, she threw a boomerang and it wouldn't even come back.
-
Ok, too bad you don't guess it. I am saying the discussion you and Rickard are having is making my day. Thanks a lot.
She's so dirty, she threw a boomerang and it wouldn't even come back.
Glad we could make you laugh. Darroll Not one person lives in the present. Only the past. I can prove it.
-
Ok, too bad you don't guess it. I am saying the discussion you and Rickard are having is making my day. Thanks a lot.
She's so dirty, she threw a boomerang and it wouldn't even come back.
I would be glad if someone could try export a function and tell me if it worked for you! Cheers! Rickard Andersson@Suza Computing C# and C++ programmer from SWEDEN! UIN: 50302279 E-Mail: nikado@pc.nu Speciality: I love C#, ASP.NET and C++!
-
I would be glad if someone could try export a function and tell me if it worked for you! Cheers! Rickard Andersson@Suza Computing C# and C++ programmer from SWEDEN! UIN: 50302279 E-Mail: nikado@pc.nu Speciality: I love C#, ASP.NET and C++!
A .def file only eliminates the need to add __declspec(dllexport) attributes alongside with each function you export. Exporting functions does not work for an exe : there is no __declspec(process) attribute. Attempting to export a .exe function using dllexport will just prompt the loading of the .dll file, which does not exist! Export interfaces instead. That's what COM is about.
She's so dirty, she threw a boomerang and it wouldn't even come back.
-
A .def file only eliminates the need to add __declspec(dllexport) attributes alongside with each function you export. Exporting functions does not work for an exe : there is no __declspec(process) attribute. Attempting to export a .exe function using dllexport will just prompt the loading of the .dll file, which does not exist! Export interfaces instead. That's what COM is about.
She's so dirty, she threw a boomerang and it wouldn't even come back.
Interesting! I used to export functions from my Delphi .exe files but had no idea that I couldn't do it in C++ - I would have had to discover that at somepoint and no doubt tear some hair out in the process. I'll have to go back to having a separate DLL to export the functions. Shame. -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
-
A .def file only eliminates the need to add __declspec(dllexport) attributes alongside with each function you export. Exporting functions does not work for an exe : there is no __declspec(process) attribute. Attempting to export a .exe function using dllexport will just prompt the loading of the .dll file, which does not exist! Export interfaces instead. That's what COM is about.
She's so dirty, she threw a boomerang and it wouldn't even come back.
In fact, I have just exported some functions from a .exe in Visual C++ and used them from a DLL! I defined them in a .def file in the .exe project and then used GetProcAddress to import them in the .dll (obviously giving the DLL function the HMODULE of my running .exe). I can send anyone who's interested the project files. -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
-
In fact, I have just exported some functions from a .exe in Visual C++ and used them from a DLL! I defined them in a .def file in the .exe project and then used GetProcAddress to import them in the .dll (obviously giving the DLL function the HMODULE of my running .exe). I can send anyone who's interested the project files. -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
Simon Steele wrote: I have just exported some functions from a .exe in Visual C++ and used them from a DLL! Lopok everyone! I told ya it was possible! Rickard Andersson@Suza Computing C# and C++ programmer from SWEDEN! UIN: 50302279 E-Mail: nikado@pc.nu Speciality: I love C#, ASP.NET and C++!
-
In fact, I have just exported some functions from a .exe in Visual C++ and used them from a DLL! I defined them in a .def file in the .exe project and then used GetProcAddress to import them in the .dll (obviously giving the DLL function the HMODULE of my running .exe). I can send anyone who's interested the project files. -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
Simon Steele wrote: I can send anyone who's interested the project files. Send me the project please. Darroll Not one person lives in the present. Only the past. I can prove it.
-
From what I know about dlls is: If my functions aren't in the def file, I cannot get a pointer to the functoins. Do you not need it in an exe? Also, will I need to export the entire class? If anyone has done this and would care to share please do. Darroll Not one person lives in the present. Only the past. I can prove it.
try something like class __declspec(dllexport) ABCD { public: void junk(){} } and if you have a simple function: int _declspec(dllexport) myfunction(); and variables: int _declspec(dllexport) myvariable; Joel Lucsy (jjlucsy@concentric.net)
-
A .def file only eliminates the need to add __declspec(dllexport) attributes alongside with each function you export. Exporting functions does not work for an exe : there is no __declspec(process) attribute. Attempting to export a .exe function using dllexport will just prompt the loading of the .dll file, which does not exist! Export interfaces instead. That's what COM is about.
She's so dirty, she threw a boomerang and it wouldn't even come back.
If you view depends on Excel you can see that Excel exports functions. Both Exes and DLLs are written in the PE format. The only difference between them is their entry point that either makes them standalone execuatable or not. So you will be able to load and EXE and map function addresses in that EXE at runtime just like it was a DLL.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life! -
If you view depends on Excel you can see that Excel exports functions. Both Exes and DLLs are written in the PE format. The only difference between them is their entry point that either makes them standalone execuatable or not. So you will be able to load and EXE and map function addresses in that EXE at runtime just like it was a DLL.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!Paul Watt (kilowatt) wrote: So you will be able to load and EXE and map function addresses in that EXE at runtime just like it was a DLL. Faking the OS by using an EXE as if it was a DLL leads you to unexpected problems. Allright, the vtable is exported and reflected by quickview or other PE viewers. Allright, you may even call a method on it. And if you are lucky, this will even work. Indeed, The process boundary and load context enabled by a standard exe launch is totally different than with a DLL (loaded in the same address space). In other words, the DLL has no context at all. You'll meet soon a guy called time chkesp.c complaining about such a use. In addition, the executable must be designed to be able to respond to your calls. Don't forget that once a process is launched, it is doing something, and is not necessarily able to respond outside calls. That's one of the benefits of using COM instead. The process life cycle raises a bunch of other troubles, but I let you discover them. Good luck!
She's so dirty, she threw a boomerang and it wouldn't even come back.
-
How do you export functions in an exe? There is no def file to use. What I want to be able to do is use an exe the same way as I do an dll. I want to be able to do the same thing as the excel.exe file. Any ideas? Darroll Not one person lives in the present. Only the past. I can prove it.
You are a lot better off making your EXE a local COM server, than trying to call in to it as if it were a DLL. COM handles all of the process/context issues for you, and you don't have to worry about calling differences between DLL's, and all that stuff. By the way: it's easy to make an existing application act as a COM server as well as continue its normal activity. Gary R. Wheeler