Exchange is built on web services and as I posted about a while about accessing EWS from SharePoint can be pretty neat. There is a managed API to make your life even easier. However, one issue you may come across is actually getting SharePoint and Exchange to talk nicely to each other. This will walk you through some of the steps required to get things going.
I'm a technical project manager, software developer and IT consultant in Guernsey, Channel Islands.
- SP2010 and Managed Metadata and &
- SharePoint 2010 + DocumentSets + OfficialFile.asmx max file size
- Current user is not a farm administrator – redux
- The OLE DB provider Microsoft.Ace.OLEDB.12.0 for linked server (null) reported an error. Access denied.
- Auto generate SQL audit tables and database triggers
- SharePoint Designer 2010 – list/library There are no items to show in this view – ListData.svc woes
- SharePoint 2010 – Managed Metadata – Required feature is not enabled for this column type
- SharePoint 2010 State Machine workflow delayActivity tip
- SharePoint 2010 State Machine workflow onWorkflowItemChanged firing multiple times
- Get SPUser from Person or Group field
- SharePoint 2010 context menu item with custom code (51)
- new SPSite – FileNotFoundException (12)
- SharePoint 2010 + Document Sets + Custom Ribbon Buttons with Custom Code (12)
- Could not load web.config file. The given key was not present in the dictionary. (11)
- SharePoint workflow + list item edit + value cannot be null (9)
Tags3g 2005 2007 2010 add bdc business data catalog comment comments contenttype custom code debugging delay activity deployment document set documentsets edit error event receiver exchange feature folders force iis infopath linkedin list definition microsoft moss powershell SharePoint sharepoint 2010 sp2010 sql sql server ssis ssms ssrs state machine workflow t-sql tip visual studio web services workflow xml content types