Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's a mess. MAPI or CDO via a .NET interop DLL is <a href="http://blogs.msdn.com/mstehle/archive/2007/10/03/fyi-why-are-mapi-and-cdo-1-21-not-supported-in-managed-net-code.aspx" rel="noreferrer">officially unsupported by Microsoft</a>--it will appear to work fine, but there are problems with memory leaks due to their differing memory models. You could use CDOEX, but that only works on the Exchange server itself, not remotely; useless. You could interop with Outlook, but now you've just made a dependency on Outlook; overkill. Finally, you could use <a href="http://msdn.microsoft.com/en-us/library/aa143161.aspx" rel="noreferrer">Exchange 2003's WebDAV support</a>, but WebDAV is complicated, .NET has poor built-in support for it, and (to add insult to injury) Exchange 2007 <em>nearly completely drops</em> WebDAV support.</p> <p>What's a guy to do? I ended up using <a href="http://www.afterlogic.com/products/net-imap-component" rel="noreferrer">AfterLogic's IMAP component</a> to communicate with my Exchange 2003 server via IMAP, and this ended up working very well. (I normally seek out free or open-source libraries, but I found all of the .NET ones wanting--especially when it comes to some of the quirks of 2003's IMAP implementation--and this one was cheap enough and worked on the first try. I know there are others out there.)</p> <p>If your organization is on Exchange 2007, however, you're in luck. <a href="http://msdn.microsoft.com/en-us/library/bb204119.aspx" rel="noreferrer">Exchange 2007 comes with a SOAP-based Web service interface</a> that finally provides a unified, language-independent way of interacting with the Exchange server. If you can make 2007+ a requirement, this is definitely the way to go. (Sadly for me, my company has a "but 2003 isn't broken" policy.)</p> <p>If you need to bridge both Exchange 2003 and 2007, IMAP or POP3 is definitely the way to go.</p>
    singulars
    1. This table or related slice is empty.
    1. PORead MS Exchange email in C#
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNicholas Piasecki
    1. USNicholas Piasecki
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORead MS Exchange email in C#
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe SOAP-based web service was wrapped by Microsoft to simplify access - it is now recommended practice to use the Exchange Web Services Managed API 1.0 SDK: http://msdn.microsoft.com/en-us/library/dd633710(EXCHG.80).aspx
      singulars
      1. PO
      1. USjlo
    2. COIt's almost as if Microsoft designed it to be inoperable with anything but Outlook
      singulars
      1. PO
      1. USChris S
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload