Compare commits
14 commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
8c3ee126a5 | ||
|
5dead96c3d | ||
|
|
b3c362a454 | ||
|
|
578f694f8a | ||
|
|
a98e01cc1c | ||
|
13fe432de6 | ||
|
|
50e7023fb1 | ||
|
|
f6f8300f9f | ||
|
a978dd78b3 | ||
|
|
f4ddc0a873 | ||
|
a8364eb91d | ||
|
|
f9167b6c95 | ||
|
c9d45b96a1 | ||
|
|
d3c89ac63d |
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
The dotnet/core repository is a good starting point for .NET Core.
|
||||
|
||||
The latest major release is [.NET 5.0](release-notes/5.0/README.md). The latest patch updates are listed in [.NET Core release notes](release-notes/README.md).
|
||||
The latest major release is [.NET 6.0](release-notes/6.0/README.md). The latest patch updates are listed in [.NET Core release notes](release-notes/README.md).
|
||||
|
||||
## .NET Core Releases
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Ubuntu | 21.04, 20.04, 18.04 | x64, ARM3
|
|||
Linux Mint | 18+ | x64 | [Linux Mint end of life announcements](https://forums.linuxmint.com/search.php?keywords=%22end+of+life%22&terms=all&author=&sc=1&sf=titleonly&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Search)
|
||||
openSUSE | 15+ | x64 | [OpenSUSE lifecycle](https://en.opensuse.org/Lifetime)
|
||||
SUSE Enterprise Linux (SLES) | 12 SP2+ | x64 | [SUSE lifecycle](https://www.suse.com/lifecycle/)
|
||||
Alpine Linux | 3.10+ | x64, ARM64 | [Alpine lifecycle](https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases)
|
||||
Alpine Linux | 3.12+ | x64, ARM64 | [Alpine lifecycle](https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases)
|
||||
|
||||
* **Bold numbers** indicate additions in this release.
|
||||
* '+' indicates the minimum supported version.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ The .NET SDK 5.0.209 release is available for download. The latest 5.0 release i
|
|||
| --------- | :------------------------------------------: | :----------------------: | :---------------------------: | :-------------------------: | :-----------------: | :-----------------: |
|
||||
| Windows | [x86][dotnet-sdk-win-x86.exe] \| [x64][dotnet-sdk-win-x64.exe] \| [Arm64][dotnet-sdk-win-arm64.exe] | [x86][dotnet-sdk-win-x86.zip] \| [x64][dotnet-sdk-win-x64.zip] \| [Arm64][dotnet-sdk-win-arm64.zip] | [x86][dotnet-runtime-win-x86.exe] \| [x64][dotnet-runtime-win-x64.exe] \| [Arm64][dotnet-runtime-win-arm64.exe] | [x86][dotnet-runtime-win-x86.zip] \| [x64][dotnet-runtime-win-x64.zip] \| [Arm64][dotnet-runtime-win-arm64.zip] | [x86][aspnetcore-runtime-win-x86.exe] \| [x64][aspnetcore-runtime-win-x64.exe] \|<br> [Hosting Bundle][dotnet-hosting-win.exe]<sup>2</sup> | [x86][windowsdesktop-runtime-win-x86.exe] \| [x64][windowsdesktop-runtime-win-x64.exe] \| [Arm64][windowsdesktop-runtime-win-arm64.exe] |
|
||||
| macOS | [x64][dotnet-sdk-osx-x64.pkg] | [x64][dotnet-sdk-osx-x64.tar.gz] | [x64][dotnet-runtime-osx-x64.pkg] | [x64][dotnet-runtime-osx-x64.tar.gz] | [x64][aspnetcore-runtime-osx-x64.tar.gz] | - |<sup>1</sup>
|
||||
| Linux | [Snap and Package Manager](../install-linux.md) | [x64][dotnet-sdk-linux-x64.tar.gz] \| [Arm][dotnet-sdk-linux-arm.tar.gz] \| [Arm32 Alpine][dotnet-sdk-linux-arm.tar.gz] \| [Arm64][dotnet-sdk-linux-arm64.tar.gz] \| [x64 Alpine][dotnet-sdk-linux-musl-x64.tar.gz] | [Packages (x64)][linux-packages] | [x64][dotnet-runtime-linux-x64.tar.gz] \| [Arm][dotnet-runtime-linux-arm.tar.gz] \| [Arm64][dotnet-runtime-linux-arm64.tar.gz] \| [Arm32 Alpine][dotnet-runtime-linux-musl-arm.tar.gz] \|[Arm64 Alpine][dotnet-runtime-linux-musl-arm64.tar.gz] \| [x64 Alpine][dotnet-runtime-linux-musl-x64.tar.gz] | [x64][aspnetcore-runtime-linux-x64.tar.gz]<sup>1</sup> \| [Arm][aspnetcore-runtime-linux-arm.tar.gz]<sup>1</sup> \| [Arm64][aspnetcore-runtime-linux-arm64.tar.gz]<sup>1</sup> \| [x64 Alpine][aspnetcore-runtime-linux-musl-x64.tar.gz] | - | <sup>1</sup> |
|
||||
| Linux | [Snap and Package Manager](../install-linux.md) | [x64][dotnet-sdk-linux-x64.tar.gz] \| [Arm][dotnet-sdk-linux-arm.tar.gz] \| [Arm32 Alpine][dotnet-sdk-linux-musl-arm.tar.gz] \| [Arm64][dotnet-sdk-linux-arm64.tar.gz] \| [x64 Alpine][dotnet-sdk-linux-musl-x64.tar.gz] | [Packages (x64)][linux-packages] | [x64][dotnet-runtime-linux-x64.tar.gz] \| [Arm][dotnet-runtime-linux-arm.tar.gz] \| [Arm64][dotnet-runtime-linux-arm64.tar.gz] \| [Arm32 Alpine][dotnet-runtime-linux-musl-arm.tar.gz] \|[Arm64 Alpine][dotnet-runtime-linux-musl-arm64.tar.gz] \| [x64 Alpine][dotnet-runtime-linux-musl-x64.tar.gz] | [x64][aspnetcore-runtime-linux-x64.tar.gz]<sup>1</sup> \| [Arm][aspnetcore-runtime-linux-arm.tar.gz]<sup>1</sup> \| [Arm64][aspnetcore-runtime-linux-arm64.tar.gz]<sup>1</sup> \| [x64 Alpine][aspnetcore-runtime-linux-musl-x64.tar.gz] | - | <sup>1</sup> |
|
||||
| | [Checksums][checksums-sdk] | [Checksums][checksums-sdk] | [Checksums][checksums-runtime] | [Checksums][checksums-runtime] | [Checksums][checksums-runtime] | [Checksums][checksums-runtime]
|
||||
|
||||
</br>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# .NET 6
|
||||
|
||||
[.NET 6](https://devblogs.microsoft.com/dotnet/announcing-net-6-rc1/) will be an [LTS release](../../release-policies.md) and will be supported for three years, from November 2021 to November 2024. It is [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](supported-os.md).
|
||||
[.NET 6](https://devblogs.microsoft.com/dotnet/announcing-net-6-rc1/) is an [LTS release](../../release-policies.md) and will be supported for three years, from November 2021 to November 2024. It is [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](supported-os.md).
|
||||
|
||||
- [Downloads](https://dotnet.microsoft.com/download/dotnet/6.0) (also see [Releases](#releases))
|
||||
- [Containers](https://hub.docker.com/_/microsoft-dotnet)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# .NET 6.0 RC2 Known Issues
|
||||
# .NET 6.0 Known Issues
|
||||
|
||||
You may encounter the following known issues, which may include workarounds, mitigations or expected resolution timeframes.
|
||||
|
||||
|
|
@ -18,76 +18,19 @@ While a lot of work has been done to support arm64 emulation of x64 processes in
|
|||
`dotnet test --arch x64` on an arm64 machine will not work as it will not find the correct test host. To test x64 components on an arm64 machine, you will have to install the x64 SDK and configure your `DOTNET_ROOT` and `PATH` to use the x64 version of dotnet.
|
||||
|
||||
#### 2. Upgrade of Visual Studio or .NET SDK from earlier builds can result in a bad `PATH` configuration on Windows
|
||||
When upgrading Visual Studio to preview 5 or the .NET SDK to RC2 from an earlier build, the installer will uninstall the prior version of the .NET Host (dotnet.exe) and then install a new version. This results in the x64 `PATH` being removed and added back. If a customer has the x86 .NET Host installed, this one will end up ahead of the x64 one and will be picked up first.
|
||||
When upgrading Visual Studio to preview 5 or the .NET SDK to RC2 from an earlier build, the installer will uninstall the prior version of the .NET Host (dotnet.exe) and then install a new version. This results in the path to the x64 copy of dotnet being removed from the `PATH` then added back. If you have the x86 .NET Host installed, it will end up ahead of the x64 one and will be picked up first.
|
||||
|
||||
Different architectures of .NET do not know about each other so then the .NET SDK will stop functioning correctly (behavior may be Visual Studio unable to create projects, dotnet new fails, etc).
|
||||
In this case you may find that Visual Studio is unable to create projects, or commands like `dotnet new` fail with a message like this:
|
||||
```
|
||||
Could not execute because the application was not found or a compatible .NET SDK is not installed.
|
||||
```
|
||||
|
||||
To confirm, run `dotnet --info` and you'll see (x86) paths for all of the found .NET runtimes and .NET SDKs installed. To resolve this, remove "c:\program files (x86)\dotnet" from the `PATH` environment variable or move it after "c:\program files\dotnet"
|
||||
To confirm, run `dotnet --info` and you'll see (x86) paths for all of the found .NET runtimes and .NET SDKs installed.
|
||||
|
||||
To fix this, edit your `PATH` environment variable to either remove the `c:\Program Files (x86)\dotnet` entry or move it after the entry for `c:\Program Files\dotnet`. Now reopen your console window.
|
||||
|
||||
## ASP.NET Core
|
||||
|
||||
### Running Blazor WebAssembly using IIS Express in Development
|
||||
|
||||
As of .NET 6 Preview 1, there is an ongoing issue with running Blazor WebAssembly applications using an IIS Express server during development on Visual Studio. As a workaround, we recommend using Kestrel during development.
|
||||
|
||||
### Incremental builds in VS not working for apps with Razor views
|
||||
|
||||
As of .NET 6 Preview 3, changes to Razor views will not be updated during incremental builds. As a workaround, you can:
|
||||
|
||||
- Build from the command line
|
||||
- Configure VS to always call MSBuild when building projects
|
||||
- Clean and build projects to pick up changes
|
||||
|
||||
### JWT Bearer Handler ArgumentOutOfRangeException in UTC+X time zones
|
||||
|
||||
As of .NET 6 Preview 5, when using the JWT Bearer handler in a time zone that is higher than UTC (e.g. Eastern European Time/UTC+2), you may observe an `ArgumentOutOfRangeException` if the JWT token does not contain a `nbf` value (valid from).
|
||||
|
||||
Issue is tracked by https://github.com/dotnet/aspnetcore/issues/33634 and will be fixed in .NET 6 Preview 6.
|
||||
|
||||
**Workaround**
|
||||
|
||||
You can workaround this by always providing a non-zero and non-minimum value for the `notBefore` parameter when using System.IdentityModel.Tokens.Jwt.JwtSecurityToken, or the 'nbf' field if using another JWT library.
|
||||
|
||||
### CPU at 100% when enabling HTTP/3 Preview
|
||||
|
||||
When enabling HTTP/3 which is only accessible through a feature flag, you might experience Kestrel using 100% of the CPU. We recommend not enabling the feature until this is fixed.
|
||||
|
||||
Issue is tracked by https://github.com/dotnet/runtime/issues/60133 and will be fixed in .NET 6 RTM.
|
||||
|
||||
|
||||
**Customizing WebRootPath not supported for minimal applications**
|
||||
|
||||
There is a known issue with modifying the `WebRootPath` in a minimal app using the `WebApplicationBuilder` as documented in https://github.com/dotnet/aspnetcore/issues/36999. The issue will be resolved in .NET 6 RTM. As a workaround, users can use the default `wwwroot` directory for serving static files in their applications. Alternatively, you can invoke `UseStaticFiles` with a `StaticFilesOption` containing both the provider and path.
|
||||
|
||||
```csharp
|
||||
app.UseStaticFiles(new StaticFileOptions
|
||||
{
|
||||
ContentTypeProvider = new PhysicalFileProvider("/full/path/to/custom/wwwroot")
|
||||
});
|
||||
```
|
||||
### Configuration not reloaded on changes
|
||||
|
||||
A regression introduced in .NET 6 RC2 prevents configuration from being reloaded on changes when using `WebApplication.Create()` and `WebApplication.CreateBuilder()`. This includes both custom configuration sources and default configuration sources such as `appsettings.json`.
|
||||
|
||||
Issue is tracked by https://github.com/dotnet/aspnetcore/issues/37046 and will be fixed in .NET 6 RTM.
|
||||
|
||||
**Workaround**
|
||||
|
||||
To make configuration reloadable in RC2, you can manually add a chained configuration source as follows.
|
||||
|
||||
```C#
|
||||
var builder = WebApplication.CreateBuilder(args);
|
||||
|
||||
var chainedConfiguration = new ConfigurationBuilder()
|
||||
.SetBasePath(builder.Environment.ContentRootPath)
|
||||
.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
|
||||
.AddJsonFile($"appsettings.{builder.Environment.EnvironmentName}.json", optional: true, reloadOnChange: true);
|
||||
builder.Configuration.AddConfiguration(chainedConfiguration.Build());
|
||||
|
||||
var app = builder.Build();
|
||||
// ...
|
||||
```
|
||||
|
||||
### SPA template issues with Individual authentication when running in development
|
||||
|
||||
The first time SPA apps are run, the authority for the spa proxy might be incorrectly cached which results in the JWT bearer being rejected due to Invalid issuer. The workaround is to just restart the SPA app and the issue will be resolved. If restarting doesn't resolve the problem, another workaround is to specify the authority for your app in Program.cs: `builder.Services.Configure<JwtBearerOptions>("IdentityServerJwtBearer", o => o.Authority = "https://localhost:44416");` where 44416 is the port for the spa proxy.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ The following [.NET releases](../releases.md) are currently supported:
|
|||
|
||||
| Version | Release Date | Support | Latest Patch Version | End of Support |
|
||||
| :-- | :-- | :-- | :-- | :-- |
|
||||
| [.NET 6](6.0/README.md) | [November, 2021](https://devblogs.microsoft.com/dotnet/announcing-net-6/) | [Preview][policies] | [6.0.0 ][6.0.0] | November 08, 2024 |
|
||||
| [.NET 6](6.0/README.md) | [November, 2021](https://devblogs.microsoft.com/dotnet/announcing-net-6/) | [LTS][policies] | [6.0.0 ][6.0.0] | November 08, 2024 |
|
||||
| [.NET 5](5.0/README.md) | [November 10, 2020](https://devblogs.microsoft.com/dotnet/announcing-net-5-0/) | [Current][policies] | [5.0.12][5.0.12] | May 08, 2022 |
|
||||
| [.NET Core 3.1](3.1/README.md) | [December 3, 2019](https://devblogs.microsoft.com/dotnet/announcing-net-core-3-1/) | [LTS][policies] | [3.1.21][3.1.21] | December 3, 2022 |
|
||||
|
||||
|
|
|
|||
|
|
@ -12,11 +12,11 @@ The following table lists in-support .NET releases.
|
|||
| Version | Release Date | Support | Latest Patch Version | End of Support |
|
||||
| :-- | :-- | :-- | :-- | :-- |
|
||||
| [.NET 6](release-notes/6.0/README.md) | [November, 2021](https://devblogs.microsoft.com/dotnet/announcing-net-6/) | [LTS][policies] | [6.0.0 ][6.0.0 ] | November 08, 2024 |
|
||||
| [.NET 5](release-notes/5.0/README.md) | [November 10, 2020](https://devblogs.microsoft.com/dotnet/announcing-net-5-0/) | [Current][policies] | [5.0.12][5.0.12 ] | May, 2022 |
|
||||
| [.NET 5](release-notes/5.0/README.md) | [November 10, 2020](https://devblogs.microsoft.com/dotnet/announcing-net-5-0/) | [Current][policies] | [5.0.12][5.0.12 ] | May 08, 2022 |
|
||||
| [.NET Core 3.1](release-notes/3.1/README.md) | [December 3, 2019](https://devblogs.microsoft.com/dotnet/announcing-net-core-3-1/) | [LTS][policies] | [3.1.21][3.1.21] | December 3, 2022 |
|
||||
|
||||
[6.0.0]: release-notes/6.0/preview/6.0.0.md
|
||||
[5.0.12]: release-notes/5.0/5.0.11/5.0.12.md
|
||||
[6.0.0]: release-notes/6.0/6.0.0/6.0.0.md
|
||||
[5.0.12]: release-notes/5.0/5.0.12/5.0.12.md
|
||||
[3.1.21]: release-notes/3.1/3.1.21/3.1.21.md
|
||||
|
||||
## End-of-life .NET versions
|
||||
|
|
|
|||
Loading…
Reference in a new issue