Hi,
As far as I know, the
There is no (and will not be) ADO.NET provider for Exchange 2000/2003. If
you want to develop pure .NET managed code you'd probably want to resort to
XML & WebDAV using HTTPRequest.
If you want to use classic ADO you need to use COM interop and point the
url to
http://servername/Exchange/username/inbox to get for example a
recordset of all items in the inbox of "username" on the Exchange server
"servername".
You also don't need to provide a connection string but rather just specify
the ADODB provider as "ExOLEDB". Note that this only works if your code
runs
locally on the Exchange 2000/2003 machine. If you want to run your code on
a remote machine you are again faced either using XML & WebDAV or ADO with
the "MSDAIPP.DSO" (Microsoft Internet Publishing Provider IIRC) which is
the only classic ADO provider supported to do remote ADO stuff.
You can check the following links for confirmation.
http://groups.google.com/group/microsoft.public.exchange.clients/browse_thre
ad/thread/955cbd8cf0cb695c/1eb4ce13fdd4546c?lnk=st&q=ado.net+%22exchange+ser
ver%22&rnum=3#1eb4ce13fdd4546c
http://groups.google.com/group/microsoft.public.in.aspdotnet/browse_thread/t
hread/c8f9ce0cbd0cec07/6bc9844028fcce1f?lnk=st&q=ado.net+%22exchange+server%
22&rnum=4#6bc9844028fcce1f
http://groups.google.com/group/microsoft.public.exchange2000.development/bro
wse_thread/thread/c269d1ffeb2a9cb/39fb5b29f284831b?lnk=st&q=ado.net+%22excha
nge+server%22&rnum=7#39fb5b29f284831b
To use WebDAV, pleaes check the following link for code samples:
http://www.independentsoft.de/webdavex/tutorial/index.html
You can also post in microsoft.public.exchange2000.development for more
information about WebDAV.
If anything is unclear, please feel free to let me know.
Kevin Yu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)