Using IMAP To Access Calendar on Exchange Server

[Guest]

Hi,

I am fairly new to .NET (coming from a Java background) and I am trying to
port an application that I originally wrote in Java, to .NET / C#. My problem
is that I cannot find a C# analog for the javax.mail library. My original
program used this to access the calendar on Exchange, via IMAP and retrieve
appointments.

I have no idea how to do this. Any help, advice, or even general guidelines
would be much appreciated. I would be very surprised if what I wanted to do
wasn't possible.

Here's a snippet of the original Java code. As you can see, it should be
fairly easy to do:

public void checkCal() {

Folder folder = null;
Store store = null;


// 1. Open the mailbox and retrieve messages
System.out.println("user: " + user + "Password: " + passwd);
URLName url = new URLName(protocol, imapHost, -1, mbox, user, passwd);
Session session = Session.getDefaultInstance(props, null);
session.setDebug(false);
store = session.getStore(url);
store.connect(); //this is a resource that needs to be cleaned up!
folder = store.getDefaultFolder();
folder = folder.getFolder(mbox);
folder.open(Folder.READ_WRITE);
int totalMessages = folder.getMessageCount();

System.out.println("Num Messages=" + totalMessages);
Message[] msgs = folder.getMessages();
FetchProfile fp = new FetchProfile();
fp.add(FetchProfile.Item.ENVELOPE);
folder.fetch(msgs, fp);
}

 

[Guest]

Oops.... what I meant to say was that I couldn't find a .NET analog for
javax.mail.... I am writing the program in C#

 

[Gerry Hickman]

port an application that I originally wrote in Java, to .NET / C#. My problem
is that I cannot find a C# analog for the javax.mail library.

Wow, the Java code looks quite elegant! I'd be interested to see side by
side compare with .NET

Exchange traditionally used MAPI, and if you do a search on "CDO" you'll
find a lot of information about the object model and what you can do
with it - including managing calendars, but I'm not sure about IMAP.
You're talking "open-standards" here, which don't always sit too well in
the Microsoft world!

One thing I did notice that's funny - the latest Exchange SDK states
that it's "not compatible with .NET" and guess what... you have to use
COM interop! I guess .NET doesn't "rock" quite as hard as we were lead
to believe in the latest press release.