Exporting a class and its derived data members in C++

You don't need to export the data members ( In fact if you export the class you can't export its members ). However the client code ( the bit that's importing on the other side ) needs to understand all the types used on the interface so it will need to include the headers e.g. windows.h that define them.

Be very careful to distinguish between exporting the class definition

class /*__declspec( dllexport/dllimport )*/ MY_API CMyClass
{
//...
};

and exporting an instance of the class

extern MY_API CMyClass AnInstance;

The first allows the client code to create its own instance of CMyClass, the second to see a single instance provided at module scope by the DLL.
If in doubt use the first technique.
One other thing: Don't have any public data members in the exported class. Use accessor functions Get, Set. It's more portable and safer that way especially when DLLs can have their own heaps and do their own memory management.

While Matthew covered most of the stuff you need to be aware of, there is one thing that may trip you up if you don't protect against it, and that's member alignment.
Have a look at #pragma pack[^]

In you header:

#ifndef __MYHEADER_H__
#define __MYHEADER_H__

#pragma pack(push,8) 

class MyClass
{
  char b;
  long long ll;
  bool b2; 
public:


  inline char getb() const { return b; }
  inline long long getll() const { return ll; }
};

#pragma pack(pop)

If client code uses a different alignment than your code was compiled with #pragma pack ensures that memory alignment stays as expected for your code.

Best regards
Espen Harlinn