Microsoft.Private.Intellisense package is not source-build friendly

[MichaelSimons]

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.

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

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.

Author:	MichaelSimons
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[ViktorHofer]

cc @carlossanlop @jeffhandley @ericstj

[ericstj]

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]

Seems like the build for this package should be something that could be done in source build, right?

Yes that would be a good solution.

Or are there non-source build friendly tools involved with packing the data in https://github.com/dotnet/dotnet-api-docs?

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]

We use an internal pipeline from the Docs Portal to generate the nupkg. I'll send you the details via chat.

[ViktorHofer]

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.