A common approach is to have a single macro (let’s call it EXPORT) which either expands to dllimport or dllexport depending on whether some sort of “building the DLL right now” define is set, like this:
#ifdef MAKEDLL
# define EXPORT __declspec(dllexport)
#else
# define EXPORT __declspec(dllimport)
#endif
class EXPORT xyz {
// ...
};
The idea is that when building your DLL, you add MAKEDLL to the preprocessor definitions. That way, all the code will be exported. Clients who link against your DLL (and hence include this header file) don’t need to do anything at all. By not defining MAKEDLL, they will automatically import all the code.
The advantage of this approach is that the burden of getting the macros right is moved from the many (the clients) to just the author of the DLL.
The disadvantage of this is that when using the code above as it is, it’s no longer possible to just compile the code directly into some client module since it’s not possible to define the EXPORT macro to nothing. To achieve that, you’d need to have another check which, if true, defines EXPORT to nothing.
On a slightly different topic: in many cases, it’s not possible (or desired!) to export a complete class like that. Instead, you may want to just export the symbols you need. For instance, in your case, you may want to just export the two public methods. That way, all the private/protected members won’t be exported:
class xyz
{
public:
EXPORT void printing();
EXPORT void printing(int a);
};