-
Notifications
You must be signed in to change notification settings - Fork 106
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
Migration to .net 8 #286
Comments
I think it's a great idea. Looked into converting some blazor projects to .net 8 myself. |
Sounds like a good plan! Have upgraded some other projects and the breaking changes are close to non-existent. |
Yep, this is definitely something I would like to see. |
Here is .net8 version. |
My company also plans to update the project using this to .NET8 soon. That said, Microsoft intends .NET6 support through Nov.12, 2024 and .NET7 through May 14, 2024. (see: https://dotnet.microsoft.com/en-us/download/dotnet) I think as a public nuget we'd ideally maintain multi-targeting (or at least publish patches for any bugs we find to versions that support .NET6/7) through those dates. We should probably be able to do that by just having multi-framework targeting in the project file. |
@TheAtomicOption PR is welcomed. |
@TheAtomicOption created other issue regarding multi framework support. |
Created issue to get some opinions.
My plan is to migrate ALL parts to .net 8 in end of dec or jan 2024.
The text was updated successfully, but these errors were encountered: