I have used the function extensively. Which is because I have worked a lot with MAPI.
I do not quite understand your question about it. It outputs the path to a directory, not a DLL. You need to find the appropriate DLL in order to call the function.
Its purpose is to provide the path of the directory where the MAPI Services file (MAPISVC.INF) and related files reside. Since I think we can safely remove MAPI capability in Hermes, as I have said before, it should be fine to remove references to this function.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it's in Winows.h I'm effed. I can't include Winows.h in an MFC app....
Regards.
FGetComponentPath is a MAPI function. It can be imported from the MAPI stub library (MAPI32.DLL) or an Outlook MAPI library (OLMAPI32.DLL).
You used this function before? Will it return the valid DLL. MAPI.DLL or
MAPI32.LL, etc? Or will I nee to #ifdef AMD64 .... etc?
Return.
On Wed, Oct 31, 2018 at 6:07 PM Pete Maclean petemaclean@users.sourceforge.net wrote:
Basically, I'll have to lift this function out of a DLL?
I'm already loading a DLL. This is a sad inidrection.
Regards,
On Wed, Oct 31, 2018 at 6:24 PM sbrothy@gmail.com wrote:
I have used the function extensively. Which is because I have worked a lot with MAPI.
I do not quite understand your question about it. It outputs the path to a directory, not a DLL. You need to find the appropriate DLL in order to call the function.
You can read more at: https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/how-to-get-path-of-specific-version-of-mapi-for-default-mail-client
It is not defined in any header file but its signature is:
typedef BOOL (STDAPICALLTYPE FGETCOMPONENTPATH)
(LPCSTR szComponent,
LPCSTR szQualifier,
LPSTR szDllPath,
DWORD cchBufferSize,
BOOL fInstall);
Its purpose is to provide the path of the directory where the MAPI Services file (MAPISVC.INF) and related files reside. Since I think we can safely remove MAPI capability in Hermes, as I have said before, it should be fine to remove references to this function.
If you need to call it then yes, you will need to load the requisite MAPI DLL and then call GetProcAddress to get the address of the function.
(AFK)
I can show you what I'm doing later....
Regards
On Wednesday, October 31, 2018, Pete Maclean petemaclean@users.sourceforge.net wrote:
--
Søren Bro Thygesen