-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
.NET 8.0 RC1 #8759
Comments
FYI I think you want this link for the RC1 announcement: https://devblogs.microsoft.com/dotnet/announcing-dotnet-8-rc1/ |
After updating to latest net8.0 RC I'm getting issue with Unsafe.AsRef call: Example code: What changed in Unsafe class part? |
After changing from DotNet 7 to DotNet 8 RC1 for webassembly browser project (not blazor), we are unable to run our application on Tizen (Samsung) and WebOS (LG) devices. After migrating to DotNet 8 RC1 we are not able to instantinate dotnet runtime at all,
do you have plans to maintain high compatibility for wasm projects in DotNet 8 or it's designed to work only with newest modern browsers? |
.NET 8 RC1 is supported in production per https://github.com/dotnet/core/blob/main/release-policies.md#support-phases. Please also see the Preview Images section in "What's new in .NET 8" as well as dotnet/dotnet-docker#4772. |
Thank you for the links. |
We previously published the stable tag (for all releases before .NET 8) starting with preview 1. That was, in retrospect, the wrong approach. We want to help people get ready for GA day. We believe that flushing the |
There is no .NET 8 ASP.NET Runtime RC Package for Is this intended? |
After I installed this version, I cannot compile applications anymore on MacOS. A project that was previously built cannot be built anymore. To be more specific, I click on the Rebuild Solution and it processes everything. But when I click on the "Run" button, I get a "The application has not been built" error. Current specs:
When I try to compile .NET 7.0 application, it does that normally. |
Update. Confirmed that it was the new .NET 8.0 RC SDK causing the problems. I followed the instructions on this page and manually removed just the SDK (I didn't remove any runtimes) and suddenly applications built on .NET 8.0 are now compiling and running successfully. |
closing in favor of #8828 |
Release Notes
.NET SDK 8.0.100-rc.1.23463.5 - September 14 2023
Today, we are releasing a new version of .NET SDK. This release suprecedes the
.NET SDK 8.0.100-rc.1.23455.8
version. The.NET SDK 8.0.100-rc.1.23463.5
is available in Visual Studio 17.8 Preview 1.This resolves an issue where the
.NET SDK 8.0.100-rc.1.23455.8
did not recognize a new certificate in MAUI optional workload. This caused the workload install to fail when using the .NET CLI. Customers would see an error even though the package was correctly signed.Please report any issues you find with .NET 8 RC 1, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Known Issues
If there are any issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.
The text was updated successfully, but these errors were encountered: