What are some good resources for learning Exchange Web Services?
I'm familiar with WebDAV and was wondering if exchange web services might be better for some integration we do with Exchange.
i wrote a wrapper library for exchange 2007 some weeks ago.
i found greg's blog pretty good.
http://gsexdev.blogspot.com/index.html
then i also found the following codeproject article extremely helpful.
http://www.codeproject.com/KB/exchange/Exchange2007EWS-Part1.aspx
good luck
There is a book on the subject from David Sterling called Inside Microsoft Exchange Server 2007 Web Services.
Book Cover http://ecx.images-amazon.com/images/I/51TFbqF1CrL._SL75_.jpg
I have found it very useful in learning about Exchange Web Services (a.k.a. EWS).
Recently, Microsoft released the client counter part of EWS dubbed EWS Managed API. It offers a much friendlier API than those generated through Visual Studio proxy class generators.
It can be downloaded at http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c3342fb3-fbcc-4127-becf-872c746840e1 and documentation can be found at http://msdn.microsoft.com/en-us/library/dd633709(EXCHG.80).aspx
Unfortunately the aforementioned book does not cover EWS Managed API since the API was released after the book.
A few blogs I found useful while researching about Exchange stuff:
Dan's WebDAV 101
Exchange API-spotting
mstehle: The CDOs and CDONTS of Messaging Development
SGriffin's MAPI Internals
Jive into Messaging world
You Had Me At EHLO
Although most of them are not specifically devoted to EWS I’ve found interesting pieces of information some way or another useful for dealing with EWS in all of them.
Related
Im working on a small project in my company where I'm using Outlook REST APIs.
https://learn.microsoft.com/en-us/outlook/rest/get-started
So far so good.
The application is also registered in Microsoft Azure Active Directory. As explained here:
https://learn.microsoft.com/en-us/graph/tutorials/angular?context=outlook%2Fcontext
Our application is permanently running and needs to get data every like 1 minute.
This causes a lot of requests.
So are there any costs regarding Microsoft Api that I should know about.
Or is the Calendar Api completely free.
Didn't find any helpful information out there so far.
Thanks in advance for any help.
Check Microsoft Graph API. Which uses all the Office 365 Apps connected with API endpoints.
Microsoft 365 pricing
I am doing integration for Evernote Business. So, I would like to know that is Evernote for Business support Rest API with OAuth2?
Evernote does not provide an official REST API; their API is Thrift-based. If you're interested in why it's Thrift-based and not REST, their former CTO discusses the reasons for that decision on their tech blog.
Tadaya Tsuyukubo has written a REST-based front end for the official Evernote API which is available here on GitHub. I haven't tried it so can't personally vouch for it. There's also a bit of discussion about it here on the Evernote discussion forum.
At work, me and my colleagues, uses geterogenous SOA. We do not use WS, prefering REST and some binary and JSON-based protocols. Due to it, we do not have WSDL-scheme of our service interfaces.
We faced problem providing information about services to our developers, cause they code in different languages, and not always posess information about all services.
The question is - how to solve this problem?
Organize wiki-system, describing each service separately? Store wsdl-like definitions in service registry? What is the best approach?
You may try "Swagger" a framework implementation for describing RESTful web services licensed under the Apache License, Version 2.0 https://developers.helloreverb.com/swagger/
My organisation has several web facing ASP.NET Web Forms Apps. They currently use Windows Authentication with impersonation enabled. The web apps are hosted internally but are exposed publicly via different domains e.g. www.abc.com & www.xyz.org.
A new requirement, is that a single log on page will be provided for all users of these apps to log in via.
Some of the solutions proposed are:
Implement an OpenId Provider backed by Active Directory (DotNetOpenAuth), modify existing apps to become relying parties of this OP.
Implement SSO through MS Forefront Threat Management Gateway.
I don't have experience with either of these. Are the proposed solutions feasible? What are the pros and cons of each? Are there other solutions that might be more appropriate?
OpenId Provider is a fairly good idea. It will be an easier route and there are some good details around the web.
You may also want to look into Active Directory Federation Services.
http://msdn.microsoft.com/en-us/library/bb897402.aspx
It is not uncommon for businesses moving to hosted solutions look to implement federated services and this is something Microsoft anticipated when setting up and creating Azure - to be corporate friendly.
They have put together a comprehensive guide here, which while not directly related to your question, does have extensive details about the technology behind federated services.
http://msdn.microsoft.com/en-us/library/windowsazure/hh127796.aspx
For more thoughts and information on, specifically the pros and cons, take a look at these articles which answer it in more depth:
http://technet.microsoft.com/en-us/magazine/ff721824.aspx
http://windowsitpro.com/active-directory/ease-cloud-security-concerns-federated-identity
http://www.csoonline.com/article/221034/the-truth-about-federated-identity-management
Some DotNetOpenAuth thoughts:
http://www.codeproject.com/Articles/325228/Choosing-technologies-for-NET-project
http://social.msdn.microsoft.com/Forums/en-US/windowsazuresecurity/thread/7a1c4e0c-346c-4008-9e5c-87ba1273b2aa/
Finally, we have personally gone with OpenAuth for one of my teams solutions. The implementation was fairly painless once we took time to really understand the RFCs (which was no easy feet, but worth taking the time to do). There are also a ton of resources on the web to get a hang of the implementation.
What I want to do with my app is accessing client's outlook, getting some data, using them to get more data from the database, and then make a file ready for blackberry to sync. All of these are better done on the server, so at the clients' end, there is only one file with everything ready, so they can easily sync it. I have searched a little, and found it is possible if I access exchange server. Could any one explain in details? I know nothing about exchange servers. Also, is there any other possible solutions?
Thank you.
Ok,
As i said you have a number of options.
I assume that you want to run this from a IIS server as you title says "Asp.Net"
Also I will assume that you want to do this in managed code. i.e not write a com object or native code.
Your options then, are to speak to exchange via web DAV , Exchange Web Services (EWS) or use a great 3rd party tool called Redemption which has RDO objects.
If you are running exchange 2007 EWS is the way to go. if you running earlier versions Web Dav is the way to go both these ways are supported by MS. RDO can be used with both versions but is supported by Dmitry Streblechenko
As far as EWS and DAV there are quite allot of resources out on the net and information on stackoverflow.
Also there are a few libraries that wrap EWS and web Dav calls up which may get you up and productive quicker.
http://www.independentsoft.com/webdavex/index.html is a good example.
EWS Resources
http://msdn.microsoft.com/en-us/library/bb204119.aspx
http://msdn.microsoft.com/en-us/library/cc540447.aspx
http://blogs.visoftinc.com/archive/2008/03/20/Using-Exchange-Web-Services-2007-The-Basics.aspx
http://www.webreference.com/programming/asp/Ajax_WebService/
WebDav
http://msdn.microsoft.com/en-us/library/aa486282(EXCHG.65).aspx
http://www.msexchange.org/articles/Access-Exchange-2000-2003-Mailbox-WebDAV.html
http://blogs.technet.com/kclemson/archive/2004/01/23/62247.aspx
http://gsexdev.blogspot.com/2005/04/aspnet-and-exchange-tips-and-samples.html
For Redemeption go to the Redemption site http://www.dimastr.com/redemption/ there are loads of examples most of them in VBA/VB but you can easliy transpose then into C#
Personaly I think that you should go down the MS supported routes first.
Marcus