You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Also documentation is not shipped with the workloads, so the IDE only shows useful help if you happen to have legacy Xamarin.Mac installed (and of course there are differences in those APIs).
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:
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:
Refs:
The text was updated successfully, but these errors were encountered: