visual c++ - VC++: Using DLLs as "subprograms" -

Then I try to put my hand on simulating after years of knowing just not to put it off and where to start I've been successful successfully to write your first emulator! Now I am organizing my code so that I can reuse the code to emulate other systems. I would like to compile my code in a shared front of the "platform operator" that will compile as what is available to my executable while I do my copy in DLLs that will be used to identify that platform operator and to be an illustration Has been done with consideration. Instead of separating my code into different projects and leaving the option to use a bulkier front-end or a streamlined "only sports" with more features, and instead of sharing the same DLLs between them Will be allowed to create two different solutions

How do I know how to compile versus DLL executables, but I do not know how to do executable links for custom Dll in this way that I can illustrate a class from it. I'm also not sure what I'm trying to do is technically possible, should the DLL class be stable? I have never coded anything like this before or have done a lot with custom DLS so that any help or ideas will be appreciated. Any advice I'm using in Visual C ++ 2010 may be thanks in advance for anyone.

You really do not have much to differentiate. Simply export your classes from Dell like you do for the function in your app, include the link to the header and the generated label as you normally do

Example.h < Pre> #ifdef DLL_EXPORT #define EXPORT_API __declspec (dllexport) #else #define EXPORT_API __declspec (dllimport) #endif class EXPORT_API example {public: see this page: Example (); ~ Example (); Int SomeMethod (); }; Int EXPORT_API Example function (); Example: Example () {// Creating Content} Example: ~ Example () {// Deleting stuff}} Example: Some Method () {// Content Back 0; } Int EXPORT_API Example () {Return 0; }

In your DLL project, define and construct DLL_EXPORT . You will get a .lib and .dll output. In your main project where you will use DLL, you do not have to do anything except the headers and links against .lib in your main project in the DLL_EXPORT symbol Do not define and ensure that .dll can get your application anywhere.

If you really want to be clever, this problem is screaming for the factory design pattern. If you design your interface well, then you can register your implementation with your DLS application, when they are loaded. You can expand forever without your main executable rebuilding.