How do I import a class into a dll?
-
Hi, I need to use a class that is outside of my DLL in my DLL. I've tried every way I know of, but I can't seem to accomplish it. I know you can export from a DLL, but can you import into a DLL? :~ The outside class is not in another DLL, it's free-standing in the project. I'm not very experienced with DLLs, so any help is greatly appreciated...Thanks!
-
Hi, I need to use a class that is outside of my DLL in my DLL. I've tried every way I know of, but I can't seem to accomplish it. I know you can export from a DLL, but can you import into a DLL? :~ The outside class is not in another DLL, it's free-standing in the project. I'm not very experienced with DLLs, so any help is greatly appreciated...Thanks!
Keylee717 wrote: it's free-standing in the project If this means the class is in source-form, then just copy it over! If it means it's part of an EXE, then Im afraid there is no easy way (if any) to import! Bikram Singh
-
Keylee717 wrote: it's free-standing in the project If this means the class is in source-form, then just copy it over! If it means it's part of an EXE, then Im afraid there is no easy way (if any) to import! Bikram Singh
Hi Bikram I would copy it over, but that class relies on other classes in the project. I can do it as a last resort and just copy all of the classes needed into the dll, but if I do that I may as well not use a dll and just put it all into the client project. Thanks for your help!
-
Hi Bikram I would copy it over, but that class relies on other classes in the project. I can do it as a last resort and just copy all of the classes needed into the dll, but if I do that I may as well not use a dll and just put it all into the client project. Thanks for your help!
Well, you needent really make a copy of the class and the classes it depends on... Just add the class and the related classes to the VC++ file view.. Keylee717 wrote: I can do it as a last resort and just copy all of the classes needed into the dll, but if I do that I may as well not use a dll and just put it all into the client project So why not use a DLL? It's always better to do that, so that in future you have only one copy of the classes to maintain. With multiple copies, you, for example, fix a bug and you've got to fix the bug in all copies... Bikram Singh