Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Latest NETStandard.Library 2.0 NuGet package contains malformed XML docs #1527

Closed
saucecontrol opened this issue Sep 9, 2019 · 8 comments
Closed
Labels

Comments

@saucecontrol
Copy link
Member

This was reported in #666 but the issue was closed since the underlying problem had been resolved for 2.1 dev builds. However, the latest available 2.0 package on NuGet (version 2.0.3) still has a malformed netstandard.xml. Is it possible to get an updated 2.0 package published with corrected docs?

@saucecontrol
Copy link
Member Author

@ericstj do you know who owns this package? I can't tell if this repo has an actual triage process in place, and this has sat for quite a while without a response.

@ericstj
Copy link
Member

ericstj commented Feb 18, 2020

@terrajobst @Anipik can you have a look?

@redoz
Copy link

redoz commented May 19, 2020

Is there a way I could rebuild this file myself using the updated tooling? Or a pre-release package somewhere with the updated xml?

@ericstj
Copy link
Member

ericstj commented May 19, 2020

You could just grab the XML from NETStandard2.1. VS uses metadata as source of truth for API, so "more" API in the XML file is not a problem. Here's where it is installed on my machine: C:\Program Files\dotnet\packs\NETStandard.Library.Ref\2.1.0\ref\netstandard2.1\netstandard.xml ; https://www.nuget.org/packages/NETStandard.Library.Ref/

@redoz
Copy link

redoz commented May 20, 2020

@ericstj Thanks, I'll give that a try!

Edit: It worked out nicely, thanks again!

@ViktorHofer
Copy link
Member

@Anipik @terrajobst this was just again reported by @KirillOsenkov in dotnet/runtime#39938.

@Anipik Anipik removed their assignment Nov 10, 2021
iamdmitrij added a commit to iamdmitrij/Tethos that referenced this issue Nov 13, 2021
@saucecontrol
Copy link
Member Author

@terrajobst, it looks like @Anipik, who was assigned to this, is no longer with MSFT. Any chance of getting someone else assigned? With NS2.0 being a relevant target for the foreseeable future, it would be really nice if we had valid docs in the ref package.

@terrajobst terrajobst added the bug label Aug 18, 2022
@terrajobst
Copy link

We decided to close this as won't fix.

It seems IntelliSense is resilient to this, it's only affecting folks who manually parse/process the documentation file. They can use the .NET Standard 2.1 package as a workaround.

@terrajobst terrajobst closed this as not planned Won't fix, can't repro, duplicate, stale Sep 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants