One of the projects that my team owns is the Concur Developer Center. Among other information, it houses the documentation for Concur's Web APIs. The documentation for the more recent API versions uses Swagger and until recently was generated by reflecting over the .NET API code. There were a bunch of problems that resulted from this approach as I'll describe in a second. But there's also some interesting trade-offs about the kind of APIs you get by focusing on service contracts as your primary design artifact.
- Page: 1 of 5