Questions about tagging within this repository / future versions about standard HOT 1 CLOSED

Closing as we don't plan to ship additional versions of .NET Standard.

• Since .NET Standard 2.1 is released, are there plans to continue development in this repository for e.g. the shared BCL going forward with .NET 5+?

No, see The Future of .NET Standard.

• Are there multiple kinds of netstandard.dll for a single .NET Standard version? E.g. are there separate versions for .NET Framework to reference and for .NET Core / .NET 5+ to reference?

Yes and no. There is a single reference assembly for a given .NET Standard version that defines the API surface. That's the DLL you compile against when you target .NET Standard.

In addition, each implementation of .NET Standard ships their own version of netstandard.dll which contains type forwards to the assemblies that implement it. .NET Framework has one, .NET Core has one, and so does Mono.

• Do the tags / branch names in this repository correspond to a .NET Standard version or something else?

We don't really use tags because our release build build process is complicated and spans multiple repos. We do, however, use branches in order to stabilize and take changes deliberately. Often, these are cherry picked commits or ported by hand, depending on complexity.

• It looks like there are patch releases; are there patch versions of a single .NET Standard version?

Patches for .NET Standard wouldn't change API versions but only build/packaging issues. And yes, we have made those changes.

• Are there other repositories which are being used to create netstandard.dll?

The reference assembly is built here, however each implementation will also have to build theirs. For .NET Core this being done in dotnet/runtime.

• Is there a way to determine, from the repository, which commit is the one used for a given release?

I don't believe so.

from standard.