Topic: To understand what not so in another's program (MS). API returns an error, but what not so does not speak.
In the first, the traditional request a subject not to transfer anywhere.
Therefore as if here prompt nothing, hardly help where still, on yours .
(M. It is necessary to hammer but I do not like to surrender at once)
(Below the link where I affected a subject)
Repeated update Win10 with v.1703 to v.1709
It is impossible to understand somehow from the analysis of distribution kit Win what files concern "function"?
Shortly about a problem, how much to a smog.
In update Win10 v.1709 MS deleted residuals "Mail Windows" (known also on XP as Outlook Express) - with . It perfectly worked as shamanism to v.1703 inclusively.
This program is necessary to me (is not considered).
By hook or by crook, I managed to recover it on v.1709 (missing files, registration of classes in the register).
But: for me does not work Simple MAPI (for example a label to Send-> the Addressee of the shortcut menu).
It was possible to understand this mechanism a little.
1) the client is installed by Defoltnyj MAPI. Registry key:
[HKEY_CURRENT_USER \SOFTWARE \CLIENTS \MAIL] @="Windows Mail"
2) It dll, responsible MAPI a functional it is registered. Registry key:
[HKEY_LOCAL_MACHINE \SOFTWARE \CLIENTS \MAIL \WINDOWS Mail] @="Windows Mail" "DLLPath" = "%ProgramFiles (x86) % \Windows THE MAIL \msoe.dll"
The essence of these two adjustments that any call in mapi32.dll is automatically broadcast in msoe.dll (on technology probably it is required 32-bit).
The call in msoe.dll precisely transits (i.e. MAPI a subsystem they not ).
E.g. to Send-> the Addressee (shortcut menu) - happens nothing (and there should be a new letter with a file)
But FixMAPI.exe works and WinMail.exe even it is short-term launched (but does nothing).
Dug more deeply:
I do a call (all parameters zero, dwRes - the result, hMapi - if f-tsija returns SUCCESS_SUCCESS == 0 here returns handle to session MAPI)
dwRes = MAPILogon (IntPtr. Zero, "", "", 0, 0, hMapi)
I tried to cause it both from mapi32.dll, and from msoe.dll in a forehead.
The result is identical, i.e. MAPI - translation in mail application works.
Only on Win10 v.1709 dwRes stablly returns
(Therefore it is obvious anything from MAPI and does not work)
And on v.1703 all OK, returns 0 + handle and MAPI is got.
Another f-tsija MAPISendDocuments function
Similarly returns 0 on v.1703 (works) and
2 == MAPI_E_FAILURE on v.1709
This business is chance somehow and to understand that to it does not suffice?
At my instruction
1) OS Win10 v.1709 (where MAPI msoe.dll it is not got)
2) OS Win10 v.1703 test (where MAPI msoe.dll OK it is got)
I like all transferred the necessary files on v.1709, the register shoveled, all like thrust.
Itself "Mail Windows" is launched and works (that already remarkably), and Simple MAPI it silently swears and is not got.
Certainly could miss something (e.g. something is not searched in the register on keywords winmail, msoe.dll, etc.)
There is any methodology to understand what exactly does not suffice for successful start e.g. f-tsii MAPILogon launched of msoe.dll?