Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish symbols for assemblies in this package #2103

Open
jdrobison opened this issue May 2, 2024 · 1 comment
Open

Publish symbols for assemblies in this package #2103

jdrobison opened this issue May 2, 2024 · 1 comment

Comments

@jdrobison
Copy link

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
Copy link
Collaborator

idg10 commented May 24, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants