WLMailApi Components:
- WLMailApiInit.dll: Contains the NktWLMailApiInit library. It contains the WLMailApiInit ActiveX object that triggers the event OnInit when the WLMail starts running and the event OnShutdown when WLMail shutdowns. Between these two events you can instance any object of WLMailApi library (see WLMailApiCom.idl) without an explicit execution of WLMail.
- WLMailApiCom.dll: This dll runs in the address space of WLMail and must be loaded by WLMailApiLoader.dll when WLMail starts running. If you instance any object of this dll (NktWLMailApi library) you launch WLMail(see in the demo application what happens if you create a toolbar and WLMail is not running) as it registers the COM server in WLMail .
NOTE: You must release all objects of this library in OnShutdown event. Otherwise, this library will not shutdown, the WLMail(wlmail.exe) process will continue running in the background and WLMail will not be able to load again.
- WLMailStore.dll: This dll contains NktWLMailStore library that lets you instance the main object FolderManager. It lets you use folders and messages. Historically you could use these objects without launching OE-WMail but currently WLMail does not support this behaviour.
- WLMailApiLoader.dll: This dll must be loaded from an application that runs from start-up. It loads WLMailApiCom.dll when WLMail is launched.
- WLMailApiAgent.exe: It's an application that runs from start-up and just loads WLMailApiLoader.dll.
Deploying WLMailApi
Working with .NET guideline
Functionality:
Local folders:
- Only local folders are supported at the moment.