exportdll DLL

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

I have a extension dll called framework.dll. I have a class in it,
declared like this

class CMetadata
{
private:
int value;
public:
GetValue();
}

In my other extension dll, I callled GetValue() using the object that
created in framework module. This object is passed into this module.
This dll impliciltly link with framework dll(has dependency of
framework.lib).

This works fine. But from my understanding, all classes or functions in
a dll must be exported from the dll in order for other module to use
it. I didn't do export here, but it it still work. Is it because I
used object that created in framework module? In this case, will the
framework's import library be empty since nothing is exported from it?

.

Relevant Pages

  • Re: exportdll DLL
    ... I have a extension dll called framework.dll. ... class CMetadata ... used object that created in framework module? ...
    (microsoft.public.vc.mfc)
  • Re: exportdll DLL
    ... In my other extension dll, I callled GetValue() using the object that ... used object that created in framework module? ...
    (microsoft.public.vc.mfc)
  • Re: calls to unmanaged dll to create a socket result in debug assertio
    ... For example, it assumes that in an extension DLL, you ... should be getting the handle of the main app from AfxGetInstanceHandle. ... the instance handle of the MFC app it is extending, that app isn't there, and it fails. ...
    (microsoft.public.vc.mfc)
  • Re: Wireless Provisioning Services and IAS Authorization DLL
    ... support to our service :-) ... | Subject: Re: Wireless Provisioning Services and IAS Authorization DLL ... |> customers needs to have somebody debug their own IAS Extension DLL then ...
    (microsoft.public.win32.programmer.networks)
  • Re: calls to unmanaged dll to create a socket result in debug assertio
    ... For example, it assumes that in an extension DLL, you ... the instance handle of the MFC app it is extending, that app isn't there, and it fails. ... Within the unmanaged code, in the DllMain procedure, I see the following ...
    (microsoft.public.vc.mfc)