Gaps found in Microsoft Exchange API documentation

TalkBack 11 of 13:

Next »

« Previous

• Thread View
• Flat View

Um. No one can write apps for Windows w/o a published API

That's why it is an API. They aren't giving away "trade secrets".

This would be similar to publishing an automotive repair manual without some key information. Now, if there is proprietary information requiring licensing, it should be announced up front. If the info was left out purposely, it should be explained where to get it and what licensing may be required. If the info is simply missing, then it needs to be corrected. In any event, sloppy.

Posted by: seanferd   Posted on: 03/12/08 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now