Skip to content

Fix API documentation #14372

Open
Open
@rolfbjarne

Description

@rolfbjarne

We currently don't have any sort of API documentation in .NET, and we'd like to fix this. Historically the documentation story for iOS has been rather complicated, where on one hand we had some manually written documentation for some of the most important iOS API, and then on the other hand we'd run a program on user's machine to import Apple's documentation that they shipped with Xcode. There were numerous problems with this approach (it was a complicated implementation and hard to maintain, it took a long time to execute on user's machines, it broke fairly often in the IDE, etc.), and it finally died when Apple changed how they stored their documentation on disk and the import tool stopped working (around Xcode 9 iirc).

Now we want to:

  • Ship at least some sort of API documentation.
  • Make the process simpler on our side (if it's easier to maintain, it's easier to make sure it doesn't bitrot as well)

The main idea behind the new plan is to use inline XML (triple-slash) documentation instead of documentation in an external repo. Hopefully this will make it much easier for us to handle/write/add to the documentation, and it will get better over time instead of worse. Using inline XML documentation is also the direction most other Microsoft teams are going.

There are multiple steps to the plan:

Relevant people outside our team:

  • Dave Britch, to help figuring out how to publish the documentation to the web site.

Refs:

Metadata

Metadata

Assignees

Labels

enhancementThe issue or pull request is an enhancement

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions