IMAPI version 2 is well designed – no arguments – file systems, recorders, data streams, notifications, dispatch interfaces to be compatible with scripting, higher level development environments and interoperation layer. Still I am armed with C++ at the very moment and back to type library imports using #import.<\/p>\n
I want to know why the hell it is required to sort out mess even between the two API modules: IMAPI2.DLL and IMAPI2FS.dll:<\/p>\n
#pragma warning(disable: 4192)
\n#import “libid:2735412F-7F64-5B0F-8F00-5D77AFBE261E” no_namespace raw_interfaces_only raw_dispinterfaces \/\/ IMAPI2
\n#import “libid:2C941FD0-975B-59BE-A960-9A2A262853A5” no_namespace raw_interfaces_only raw_dispinterfaces exclude(“_IMAPI_MEDIA_PHYSICAL_TYPE”, “IDiscRecorder2”) \/\/ IMAPI2FS
\n#pragma warning(default: 4192)<\/p><\/blockquote>\nIn order to import into C++ project, it is required to exclude two items which are duplicate between the modules. OMFG.<\/p>\n
Still it is not the end. Since I am subscribing to events using ATL’s IDispEventImpl<\/a> and SINK_ENTRY_EX<\/a>, I need DISPID<\/a> values for the Update methods of DDiscFormat2DataEvents<\/a> and DFileSystemImageEvents<\/a>. How do I find them? Type library as usual? No, my dear friend, type library does not mention this useless value… For further reference:<\/p>\n
\n
- DFileSystemImageEvents::Update – DISPID is 256<\/strong><\/li>\n
- DDiscFormat2DataEvents::Update – DISPID is 512<\/strong><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
IMAPI version 2 is well designed – no arguments – file systems, recorders, data streams, notifications, dispatch interfaces to be compatible with scripting, higher level development environments and interoperation layer. Still I am armed with C++ at the very moment and back to type library imports using #import. I want to know why the hell… <\/p>\n