|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
C# and Exchange Server 2007I'm an experienced .NET developer, and have recently acquired a new project which will require a C# WinForms (VS.NET 2005) desktop app to interface with Exchange Server 2007. Specifically, it will need to open a mailbox and iterate through the mail messages looking for any with specific subjects. If found, the app will need to fetch the contents of the mail message (including any attachments), and then delete the message. I'm looking for some initial guidance as to the best way to approach this, as I don't have any experience of interfacing with Exchange Server 2007. I have no problem using a 3rd-party component if that is the best way to go... Any assistance gratefully received. Mark Hello,
if your application will solely work against an Exchange 2007, you should probably stick to the Exchange Webservices. If you want to use WebDAV, I have written a .NET library, which wraps most of the low-level operations. See http://www.infinitec.de/libraries/exchange/enumeratingattachmentsininbox.aspx for an example. It's pretty close to what you are trying to accomplish. Best regards, Henning Krause Show quote "Mark Rae" <mark@markNOSPAMrae.com> wrote in message news:ermcCmRdHHA.4188@TK2MSFTNGP02.phx.gbl... > Hi, > > I'm an experienced .NET developer, and have recently acquired a new > project which will require a C# WinForms (VS.NET 2005) desktop app to > interface with Exchange Server 2007. > > Specifically, it will need to open a mailbox and iterate through the mail > messages looking for any with specific subjects. If found, the app will > need to fetch the contents of the mail message (including any > attachments), and then delete the message. > > I'm looking for some initial guidance as to the best way to approach this, > as I don't have any experience of interfacing with Exchange Server 2007. > > I have no problem using a 3rd-party component if that is the best way to > go... > > Any assistance gratefully received. > > Mark > "Henning Krause [MVP - Exchange]" <newsgroups_rem***@this.infinitec.de> Yes - the current requirement is that it must interface with Exchange 2007 wrote in message news:exUbg0TdHHA.4516@TK2MSFTNGP04.phx.gbl... > if your application will solely work against an Exchange 2007, only. > you should probably stick to the Exchange Webservices. OK - I'll look into that.> If you want to use WebDAV, I have written a .NET library, which wraps most I don't particularly want to use WebDAV unless it's the best option - I will > of the low-level operations. See > http://www.infinitec.de/libraries/exchange/enumeratingattachmentsininbox.aspx > for an example. It's pretty close to what you are trying to accomplish. check out your link. Thanks. I would stick to exchange web services are much easier to work with
than web dav http://msdn2.microsoft.com/en-us/library/aa562613.aspx regards Show quote On Apr 2, 8:51 pm, "Mark Rae" <m...@markNOSPAMrae.com> wrote: I> "Henning Krause [MVP - Exchange]" <newsgroups_rem***@this.infinitec.de> > wrote in messagenews:exUbg0TdHHA.4***@TK2MSFTNGP04.phx.gbl... > > > if your application will solely work against an Exchange 2007, > > Yes - the current requirement is that it must interface with Exchange 2007 > only. > > > you should probably stick to the Exchange Webservices. > > OK - I'll look into that. > > > If you want to use WebDAV, I have written a .NET library, which wraps most > > of the low-level operations. See > >http://www.infinitec.de/libraries/exchange/enumeratingattachmentsinin... > > for an example. It's pretty close to what you are trying to accomplish. > > I don't particularly want to use WebDAV unless it's the best option - I will > check out your link. > > Thanks. Hello,
I agree under these circumstances: - You must do the entire webdav stuff yourself. The library I built takes most of the hassle away here - You code solely against mailboxes. Exchange 2007 WebServices do not cover public folders. So if you now built your solution on Exchange WebServices only, and your requirements suddenly change (which they unfortunately tend to), you must rebuilt everything using WebDAV again... Best regards, Henning Krause Show quote "kaza" <kaza***@gmail.com> wrote in message news:1176920101.179516.207480@b75g2000hsg.googlegroups.com... >I would stick to exchange web services are much easier to work with > than web dav > http://msdn2.microsoft.com/en-us/library/aa562613.aspx > > regards > > On Apr 2, 8:51 pm, "Mark Rae" <m...@markNOSPAMrae.com> wrote: >> "Henning Krause [MVP - Exchange]" <newsgroups_rem***@this.infinitec.de> >> wrote in messagenews:exUbg0TdHHA.4***@TK2MSFTNGP04.phx.gbl... >> >> > if your application will solely work against an Exchange 2007, >> >> Yes - the current requirement is that it must interface with Exchange >> 2007 >> only. >> >> > you should probably stick to the Exchange Webservices. >> >> OK - I'll look into that. >> >> > If you want to use WebDAV, I have written a .NET library, which wraps >> > most >> > of the low-level operations. See >> >http://www.infinitec.de/libraries/exchange/enumeratingattachmentsinin... >> > for an example. It's pretty close to what you are trying to accomplish. >> >> I don't particularly want to use WebDAV unless it's the best option - I >> will >> check out your link. >> >> Thanks. > > I >  |
|||||||||||||||||||||||
Other interesting topics