-
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 6 Preview 5 #6389
Comments
Hi, I'm blocked by the JWT Handler issue which occurs after migrating from preview 4 to preview 5 |
Hi. After migration from preview 4 to preview 5 |
Hi, I'm getting this error "error NU1102: Unable to find package System.ComponentModel.Annotations with version (>= 6.0.0-preview.5.21217.1) - Found 57 version(s) in nuget.org [ Nearest version: 6.0.0-preview.4.21253.7 ]" after upgrading from preview 4 to 5. |
Web API server fails to start when you have more than 3 hosted services registered. Error message: System.InvalidOperationException: Server has already started. Steps to reproduce:
It will work if you launch it from the solution root and specify a --project flag. But it won't serve any Blazor content. And this can be counted as another issue I guess. |
Adding @danroth27 and @LadyNaggaga to see if these issues are already being tracked |
@hmsca See dotnet/announcements#190. System.ComponentModel.Annotations is now part of the shared framework in .NET 6, so you should remove the package reference. |
@BrennanConroy @shirhatti Was this an intentional change in behavior? |
@halter73 This looks like they're using |
Hi again. After migration from preview 4 to preview 5 |
Thanks for the report @hmsca! This is being tracked by dotnet/aspnetcore#33795. For anyone wanting a workaround, you could do something like the following to get an absolute path: var absolutePath = Path.Combine(builder.Environment.ContentRootPath, "www");
builder.WebHost.UseWebRoot(absolutePath); |
.NET 6 Preview 5, Blazor Webassembly has issue's with some of the Chrome Client and Firefox which results in halting the total functionality of the web app, Here is the Console Print
|
When I upgrade .NET 6 preview 4 to preview 5, I'm using a new
You can find my sample code here if needed |
@danroth27, the comment you left here https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-5/#comment-3439 solved my issue. Upgrading Microsoft.VisualStudio.Web.CodeGeneration.Design from 6.0.0-preview.5.21313.1 to 6.0.0-preview.5.21321.1 did the job! Thank you 👍 |
Namespace changed from |
Does anyone know whether this comes pre-installed in Windows 11? |
@shrinidhi111 .NET 6 is not installed with Windows 11. |
@smjltd Thanks for reporting this! Could you please open an issue in the https://github.com/dotnet/aspnetcore/issues/new with details on how to reproduce the error you're seeing? |
Just a little thing I noticed - if you use Add/Remove programs to uninstall the SDK, it actually leaves the folder behind with a zero-byte file in it in C:\Program Files\dotnet\sdk. This confuses dotnet.exe into thinking the SDK is installed, yet doesn't have a dotnet.dll in it. I deleted the folder by hand and now dotnet.exe --info lists only the real SDKs I have installed, and has started working again. Seems like the installer just needs to make sure the folder is removed. |
Appsettings do not merge. Example: export ASPNETCORE_ENVIRONMENT=Development Result: { "Logging": { "LogLevel": { } } } |
@vahpetr this looks like separate issue, can you please create a new one? |
closed in favor of #6467 |
faced same issue while updating the dotnet 6 preview 4 to preview 6. i fixed by creating new blazor webassembly project using preview 6. and then replaced App.razor file
this was the change i noticed also removed below refrence from .csproj file |
Release Notes
Please report any issues you find with .NET 6, 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: