RussKie
commented
1 month ago This item has been long on a backlog with some progress. It is hard to tell from the issue whether it is something you've already figured out or you're just planning to.
Essentially, Microsoft.Private.Winforms is the package that contains triple-slash docs, which are ingested by the docs system. However, when I worked on this, the docs system would only ingest the new docs and won't update any of the existing. To make the code the source of truth, we'd need to import all existing triple-slash docs from the docs system. That was meant to be achievable by the DocPorting tool which @jeffhandley and @carlossanlop worked on. Once all the existing triple-slash docs are imported into the codebase, the docs system will need to be reconfigured to ingest all incoming docs from the source.
Back in the days, with the docs team we discussed possibilities of creating two flows: source->docs and docs->source, but I don't know whether this story had any progress since then.
lonitra
Currently we need to manually port any new documentation to the dotnet-api-docs repo when it comes time to documenting new APIs that have been added in the release cycle. We should investigate making our source code documentation the source of truth so that we reduce the manual effort that occurs when it comes time to documenting new APIs for the release cycle.
In runtime repo, this has already been achieved for some projects by creating a transport package that automatically pushes the ref assemblies and the intellisense files to a feed where the dotnet-api-docs repo consumes that package to update the Microsoft Learn website.