Repository navigation
Microsoft.Private.Intellisense package is not source-build friendly #77004
Description
Currently the Microsoft.Private.Intellisense documentation package is treated as a text-only reference package for source-build. This pattern works well when package versions are fairly static for a release. Every time the package version changes, the source-build reference package must be updated otherwise it will cause a prebuilt in source-build. Because the Microsoft.Private.Intellisense package changes regularly, this causes maintenance burden. It would be preferred if we can find a more friendly way to handle this package.
Activity
ViktorHofer commentedon Oct 13, 2022
cc @carlossanlop @jeffhandley @ericstj
ericstj commentedon Oct 13, 2022
Seems like the build for this package should be something that could be done in source build, right? Or are there non-source build friendly tools involved with packing the data in https://github.com/dotnet/dotnet-api-docs?
MichaelSimons commentedon Oct 13, 2022
Yes that would be a good solution.
I'm not finding the infrastructure logic in the repo that handles the packaging of the ref doc into Microsoft.Private.Intellisense.nupkg. I do see a dependency on buildcore which I am unfamiliar with. Who is familiar with how the build works? Aside from the build details, my first thought is this would have to be added to source-build-externals given it doesn't utilize arcade to build.
carlossanlop commentedon Oct 13, 2022
We use an internal pipeline from the Docs Portal to generate the nupkg. I'll send you the details via chat.
ViktorHofer commentedon Jul 12, 2023
This package continues to be non source build friendly. The ideal path forward is making progress on the triple-slash XML source-of-truth effort in runtime to make the package's usage obsolete. Meanwhile, we will probably need to add SBRP for it throughout the release.