Calculate .NET API URLs without xrefmap

[yufeih]

Xrefmap represents an ID -> object mapping and is a general-purpose cross-referencing mechanism used in many places. For .NET API reference, using xrefmap as intermediary has limitations such as missing info for <inheritdoc />. In addition, the xref service in MSLearn for .NET BCL may be retired in the future. We’d like to move to a future where API URLs are calculated using URL patterns.

• calculate MSLearn URL
• calculate PDB symbol link URL
• drop useCompatibilityFileName
• calculate internal API cross-linking
• allow cross-linking APIs to dependency sites

[KalleOlaviNiemitalo]

How is inheritdoc going to work with the uid-url mapping; will it require local xml doc files for the assemblies in which the interfaces and base classes are defined?

[yufeih]

How is inheritdoc going to work with the uid-url mapping; will it require local xml doc files for the assemblies in which the interfaces and base classes are defined?

It'll work the same way as visual studio using XML doc file for assemblies and source code for C# files.