February 2, 2012
In Dovetail Agent, there has been support for a long time to integrate Microsoft Outlook into the email functionality. In the past this has been done by using Collaboration Data Objects (CDO), which is a 32-bit client library that provides access to Outlook-compatible objects through a COM-based API. As customers (and Dovetail Software employees) upgraded to Office 2010 (x64), the Outlook integration solution that tried to load the 32-bit CDO ActiveX controls or DLLs did not work. The resolution for this issue was to migrate Dovetail Agent from using CDO to use the Outlook Object Model (OOM). Opening the Session with Outlook The first step was to get access to the Outlook Object Model (OOM). In Dovetail Agent 4.5, the method for opening a session was to create a MAPI session from CDO, and then log on using the default…
Moving from CDO to the Outlook Object Model
February 2, 2012
In Dovetail Agent, there has been support for a long time to integrate Microsoft Outlook into the email functionality. In the past this has been done by using Collaboration Data Objects (CDO), which is a 32-bit client library that provides access to Outlook-compatible objects through a COM-based API. As customers (and Dovetail Software employees) upgraded to Office 2010 (x64), the Outlook integration solution that tried to load the 32-bit CDO ActiveX controls or DLLs did not work. The resolution for this issue was to migrate Dovetail Agent from using CDO to use the Outlook Object Model (OOM). Opening the Session with Outlook The first step was to get access to the Outlook Object Model (OOM). In Dovetail Agent 4.5, the method for opening a session was to create a MAPI session from CDO, and then log on using the default…
October 5, 2010
I had recently blogged about a security vulnerability in ASP.NET. Microsoft has released a security fix for this issue that is available through Windows Update. Details and frequently asked questions are available. Please make sure to install these updates as soon as possible on your servers.
July 29, 2010
We ran into trouble with a web applications deployment of our only .Net product without a windows installer. Little did we know when you zip up a web application, have your on-site expert consultant download said zip file and extract it with Windows Explorer (Note: it does not happen with WinRar or 7zip) You will run into this exception trying spin up that web application. Security Exception Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file. Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of…