I realise that the MAPISVC.INF file will not normally change. When you are testing your project in Visual Studio, you might like to include this Post Build Event in your project properties: rundll32 $(TargetPath) MergeWithMAPISVC Now when you build your project, the entries in MAPISVC.INF will refresh automatically. The magic happens in MergeWithMAPISVC and GenerateProviderPath. To demonstrate this, I’ve updated the over on Codeplex. You will see failures if you choose a path which contains characters cannot survive such a roundtrip through /. The path you use may be converted to and from Unicode using the code page provided.Update: this was fixed in Outlook 2013 () and Outlook 2010 ( So you cannot use paths such as “c:my.” or “c:”. This means that paths which contain other periods cannot work. Because Outlook’s MAPI was not originally designed with full paths in mind, it does this insertion of the “32” by looking for the first period in the string.
So if you register the path “c:mypathmyprovider.dll”, MAPI will try to load “c:mypathmyprovider32.dll”. In both cases, this full path must be without the “32” suffix, as MAPI will continue to append it before looking for your file.If you’re using full paths in MAPISVC.INF, you must use the same path in WrapStoreEntryID. Further, in a store provider, you will from time to time generate entry IDs using WrapStoreEntryID, which takes as a parameter the name of your provider.When registering your provider in MAPISVC.INF, you should put the full path to the provider in PR_SERVICE_DLL_NAME and PR_PROVIDER_DLL_NAME.Outlook development has agreed to support this for Outlook 2010 and higher. However, it turns out that, with a few restrictions, Outlook’s MAPI can deal with full paths to MAPI providers. What if, like any other modern application, you want to drop your provider over in Program Files and not dirty the path? According to the MAPI documentation, you shouldn’t be able to do that. MAPI will then load your provider by looking for it on the path. For both properties, you are expected to set the name of your provider’s DLL (minus the “32” suffix'). You Will Never Know Imany Download Zippy Share there. One is PR_SERVICE_DLL_NAME, set in the, and the other is PR_PROVIDER_DLL_NAME, set in the section. There are a few standard properties set during this configuration which tell MAPI where to find your DLL.
Return type: void // Argument: LPSTR.Īs you know, when you install a new provider on a system, you have to update to point it to the new provider. Where did MAPISVC.INF go? This will get the correct path to the MAPISVC.INF file.
The entries in MAPISVC.INF will refresh automatically.
0 kommentar(er)
