NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #632 most downloaded on NuGet
This Windows Compatibility Pack provides access to APIs that were previously available only for .NET Framework. It can be used from both .NET as well as .NET Standard.
Latest stable
11.0.0
Last release 8 days ago
10 Nov 2026
Ships on a steady schedule
a new release about every 4 weeks
Some releases are documented
notes for 15 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
127 years old
107 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Your coding agent can read these notes before it upgrades. Set up the MCP server →
You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.10 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.10 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.8 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.8 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.7 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.7 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.6 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.6 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8 from the repository by cloning the release tag v8.0.5 and following the build instructions in the main README.md.
You can build .NET 8 from the repository by cloning the release tag v8.0.5 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.4 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.4 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.3 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.3 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.2 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.2 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
You can build .NET 8.0 from the repository by cloning the release tag v8.0.1 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.1 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dotnet.microsoft.com/download/dotnet/release-key-2023.asc
You can build .NET 8.0 from the repository by cloning the release tag v8.0.0 and following the build instructions in the main README.md.
You can build .NET 8.0 from the repository by cloning the release tag v8.0.0 and following the build instructions in the main README.md.
Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dotnet.microsoft.com/download/dotnet/release-key-2023.asc
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Because the drawbacks of Product Construction v1 made it unsuitable for day-to-day development and because .NET Core 3.0 was a significantly more comp
Because the drawbacks of Product Construction v1 made it unsuitable for day-to-day development and because .NET Core 3.0 was a significantly more complex product than 2.1, .NET decided to move back towards the Product Construction v0 methodology for .NET 3.0 and onward. Essentially, orchestrate the .NET build from the bottom up (repo-repo relationships) instead of the top down. To reduce cost, we decided to rewrite the dependency flow system to enable better UX and flow control and added shared tooling via Arcade to enable consistency across repositories. You can read more about these changes in: The Evolving Infrastructure of .NET Core and A Deep Dive into How .NET Builds and Ships .
For most cases, Product Construction v2 is a significant improvement over either previous Product Construction systems. The dependency flow system (Maestro++), in particular, is much more flexible, self-service, and easier to understand than previous iterations. Unfortunately, the ease of dependency flow has actually led to a more complex build. Because more repositories could participate and introduce new relationships, they did. This strains .NET's ability to build and ship. A single commit in a repository at the base of the dependency flow graph might lead to dozens of eventual commits in downstream repositories. Cross-stack changes are still expensive to make. Maintaining source-build in the face of this complexity is harder than ever. Furthermore, the infrastructure required to produce a full .NET build (as opposed to a source-built SDK) really only exists within Microsoft's labs, and even Microsoft's own .NET developers struggle to work efficiently. This is a hindrance to the .NET community.
Again, we need a new methodology.
Nothing published for this version
On one hand, it was easy to determine what the state of a build was. It was easy to deal with security fixes. It produced builds relatively quickly co…
Product Construction v1 was an attempt to lower the cost of builds and produce them faster. ProdCon, as it was informally called, produced builds of .NET by sequentially launching the official builds of the "core repositories" of .NET and feeding the outputs of each one into the next. For example, coreclr would build, then ProdCon would feed the packages produced into the corefx build, and so on. The key difference between ProdCon and Product Construction v0's approach is that ProdCon orchestrated the build from the top down, rather than letting repositories orchestrate it from the bottom up. Dependency flow was done without commits to each repo. The orchestration system simply overrode the input package versions of dependent repositories with the outputs of previous legs, and then told the build where to put the outputs.
Again, this system worked, but had serious drawbacks. On one hand, it was easy to determine what the state of a build was. It was easy to deal with security fixes. It produced builds relatively quickly compared to previous systems. On the other hand, it had no way to deal with breaking changes, making it prohibitive for use in early product development phases. Because dependency flow was not implemented with repository commits, building a shipping commit for a repository wouldn't produce the same build that ProdCon created. Reproducing official builds was expensive and required specialized knowledge.
Again, .NET decided to try a different approach (Product Construction v2).
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.