I have a COM Shim for an Outlook XP Addin that is intended to be registered as trusted code in the "Outlook Security Settings" public folder on an Exchange Server. The code is developed in C/C++. It is not .NET so it is not managed code. The Addin always loads and its access to the OOM is derived from the Application object. However, if the DLL is not registered on the Exchange server as "Trusted Code", access to the message body triggers the OM Guard. If it is trusted, then the guard does not pop up. There will be situations where the system Administrator has forgotten to register the DLL with the Admin Pack. I'd like to know in advance if the DLL was not trusted and skip certain portions of my code that would cause the warning to appear. i.e operate with limited functionality if the DLL was not trusted. How can I determine at run-time if the DLL is trusted? Is there an API to interrogate the Exchange server or is there some code that I can put in a Try/Catch block to identify an untrusted DLL?
