All issues

Search results

When a type is marked forInternalUseOnly no docs should be ported

Status: Open.

#182In dotnet/api-docs-sync;

· ericstj opened on Oct 6, 2025

PortToDocs interprets [x](y) as a hyperlink

Status: Open.

#181In dotnet/api-docs-sync;

· ericstj opened on Sep 30, 2025

Para tags are mangled when explicitly declared in remarks in combination with new-lines

Status: Open.

#180In dotnet/api-docs-sync;

· ericstj opened on Sep 29, 2025

PortToDocs changing many docs which aren't touched by intellisense input

Status: Open.

#179In dotnet/api-docs-sync;

· ericstj opened on Sep 26, 2025

PortToDocs adding inheritdoc for types which aren't publicly documented

Status: Open.

#178In dotnet/api-docs-sync;

· ericstj opened on Sep 25, 2025

PortToDocs tool adding seealso elements which duplicate existing altmember elements

Status: Open.

#177In dotnet/api-docs-sync;

· ericstj opened on Sep 24, 2025

PortToDocs tool changing line endings or whitespace and nothing else

Status: Open.

#176In dotnet/api-docs-sync;

· ericstj opened on Sep 24, 2025

Too many \<para> tags added when importing docs from IntelliSense

Status: Open.

#175In dotnet/api-docs-sync;

· gewarren opened on Oct 17, 2024

PortToTripleSlash might not be working with Microsoft.BCL assemblies

port-to-tripleslash

Status: Open.

#167In dotnet/api-docs-sync;

· carlossanlop opened on Aug 24, 2023

PortToDocs fails and exits when encountering a malformed xml

port-to-docsIssues related to the PortToDocs tool.Issues related to the PortToDocs tool.

Status: Open.

#166In dotnet/api-docs-sync;

· carlossanlop opened on Aug 23, 2023

Missing item in dotnet-api-docs removes the existing item in triple slash

port-to-tripleslash

Status: Open.

#163In dotnet/api-docs-sync;

· carlossanlop opened on Apr 19, 2023

Some projects can't be ported immediately after building all runtime

port-to-tripleslash

Status: Open.

#162In dotnet/api-docs-sync;

· carlossanlop opened on Apr 19, 2023