I have stumbled upon couple of good resources for Exchange and Office Development last week while researching for an issue.
If you would like to take advantage of access to information about protocols, file formats, standards and other technical specifications for Microsoft high-volume products then visit Open Specifications Developer Center . As part of an on-going commitment to providing interoperability with Microsoft products, the Learn Open Specifications and Interoperability page (also referred to as the Learn Tab) in the Open Specifications Developer Center page hosts instructional content about protocols, file formats, standards and other technical specifications for Microsoft products. Learning modules bring together content from MSDN, Channel 9, and other Microsoft websites, making them the “one-stop shopping” solution for common interoperability topics.
Also if you have not discovered the Open Specifications Interactive Pivot yet? then explore it Open Specifications Interactive Pivot, which makes it easy to find the Open Specifications documents you need in a visual, intuitive way. The Pivot uses Silverlight Deep Zoom technology, which lets you visually search and filter the open specifications documents. Once you use it, you’ll see why we’re excited. The Pivot currently features Exchange, Internet Explorer, Lync, Microsoft Office, and SharePoint protocols. In upcoming months, we plan to add Windows and SQL Server.
And not forget to visit Office Developer Center to find developer resources for creating custom solutions with Microsoft Office 2010, 2007, and 2003.
One of my interesting find on it is Microsoft Office 2010 Developer Map, the Microsoft Office 2010 Interactive Developer Map is a Silverlight application that helps developers visualize the different kinds of applications, services, client/server data-access technologies, on-premise servers, platform products and technologies, and tools that can help developers build multiple line-of-business solutions.
The map is a living document that provides links to MSDN Library reference documentation, MSDN portal pages, videos, and RSS feeds that describe how developers can use Office 2010 and associated tools and technologies to develop solutions that meet their needs. It allows them to drill down to each product and technology and learn about new features, objects, web services, protocols, and content resources that show you how to use and extend Microsoft Office and build custom solutions.
I would like to share that Microsoft® Script Explorer for Windows PowerShell® (pre-release) is available on Microsoft Download Center.
Microsoft® Script Explorer for Windows PowerShell® (pre-release) helps scripters find Windows PowerShell scripts, snippets, modules, and how-to guidance in online repositories such as the TechNet Script Center Repository, PoshCode, local or network file systems and Bing Search Repository. Microsoft® Script Explorer enables:
Here the snapshot of this cool tool:
Download it @ Microsoft Script Explorer for Windows PowerShell (pre-release)
If you are using EWS Java API 1.1 provided by Microsoft @ http://archive.msdn.microsoft.com/ewsjavaapi and facing some issues related to it, then feel free to report such issues to below mentioned forum to seek assistance: Exchange Server TechCenter > Exchange Server Forums > Development > http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads
I would highly recommend you to prefix the question title as [Ex20XX] [EWS JAVA API 1.X]… so that the members of the forum could easily review/relate the questions specific to EWS JAVA API.
You must be wondering that why I haven’t suggested you to contact Microsoft Support?
Basically, if we have closer look at license agreement under which Microsoft has published the EWS Java API, you would see:
9. SUPPORT SERVICES. Because this software is “as is,” we may not provide support services for it.
Its clearly mentioned that EWS JAVA API is provided on “as is” basis, therefore the recommendation above.
However, if you are able to repro the issue using the EWS SOAP Request(outside of Java code) or using Microsoft Exchange Web Services Managed API 1.2 against recent build of Exchange 2007/2010 then please report the issue to http://support.microsoft.com. we would be more than happy to assist you with the issue.
We could also use handy utility like EWS Editor available @ http://EWSEditor.codeplex.com published by Matt Stehle(mstehle: The CDOs and CDONTS of Messaging Development) to repro the issue outside of Java and that would help us understand if the issue is specific to EWS JAVA API or EWS protocol.
As mentioned earlier, if we happen to find issue specific to EWS protocol or EWS Managed API then we could definitely take up that issue with Microsoft Product group.
Hope this helps!