Microsoft Opens Up APIs, Protocols -- Visual Studio Magazine

Desmond File

Microsoft Opens Up APIs, Protocols

Michael Desmond, founding editor of Redmond Developer News and Desmond File blogger, is on vacation. Filling in for him today is Kathleen Richards, senior editor of RDN. You can reach her at [email protected].

Big interop news out of Redmond this morning. As reported by my RDN colleague Jeffrey Schwartz, Microsoft is making a push to be more open:

"In a major shift in its business model, Microsoft today said it is placing a significant emphasis on standardization and interoperability, saying it will share its APIs, release extensive documentation of its protocols, and is promising not to sue open source developers who use Microsoft's patented protocols for non-commercial implementations."

Read the rest of the story here. --Kathleen Richards

Posted on 02/21/2008

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.