PortToTripleSlash might not be working with Microsoft.BCL assemblies

Open
#167 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
documentation

Research direction

Start by running the reported PortToTripleSlash command against Microsoft.Bcl.Numerics.csproj, using the dotnet-api-docs/xml path and the listed assemblies and namespace. Investigate whether Microsoft.BCL assemblies are processed correctly; done means the command reliably produces the expected triple-slash documentation for those assemblies.

Written by the indexing model from the issue text.

Description

port-to-tripleslash

cc @michaelgsharp

Need to investigate this:

PortToTripleSlash  -CsProj C:\repos\runtime\src\libraries\Microsoft.Bcl.Numerics\src\Microsoft.Bcl.Numerics.csproj  -Docs C:\repos\dotnet-api-docs\xml  -IncludedAssemblies "System.Runtime,System.Private.CoreLib,Microsoft.Bcl"  -IncludedNamespaces System
Dominant language
C#
Stars
14
Forks
21
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/api-docs-sync

All issues in dotnet/api-docs-sync

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.