search

dotnet / reactive

The Reactive Extensions for .NET
http://reactivex.io
MIT License
6.57k stars 736 forks source link

Publish symbols for assemblies in this package #2103

Open jdrobison opened 2 months ago

jdrobison commented 2 months ago

Code that references this package will generate a SymbolCheck error when verifying that symbols are available for assemblies it uses, such as system.interactive.async.dll and system.linq.async.dll.

See https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2047053

idg10 commented 1 month ago

Could you clarify what you mean by "this package"? There are several packages in Rx.NET.

We publish symbols to NuGet so I'm not sure what it is you're asking us to do.

Also, that work item does not appear to be publicly visible. I'm guessing that "devdiv" is a Microsoft Azure DevOps account, so I'm wondering if perhaps you are under the impression that Rx.NET is a Microsoft project? It was a long long time ago (well over10 years ago), hence the use of System.* namespaces and its presence in the dotnet org, but it has been a community-supported .NET Foundation project for many years now.

None of the currently active maintainers on this project works for Microsoft. So aside from the permission we have to use System package prefixes and namespaces (required for backwards compatibility), and the fact that the .NET Foundation signs our binaries for us, we don't get to do anything when publishing our packages that any random member of the public couldn't do. And as far as I know, publishing symbols to NuGet is the only option open to us.