-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
Port to .NET 6+ #1141
Comments
cefsharp/CefSharp#2796 Seems to be getting closer. |
Are we waiting for the integration to improve now? |
I'm not going to port to Core 3.0. I don't think it's a good idea to use such fresh release. Current plan is to port to .NET 5, which should release next year (and be more battle tested). |
How is this coming along? I'm willing to help, if needed |
I have plans to start looking into it more after .NET 6 is out. Don't need help with it really, since it's a critical change and I want to have full control over it. |
Any news on this, as .NET 6 has been released. My guess this is some corner stone for cross platform compatibility. |
No news, it won't happen sooner than next year (most likely with 6.1). It's not corner stone for cross platform compatibility, see #59 |
Was wondering how things were going with regards to this issue and if I could be of any help? |
Planned for Playnite 11. I'm currently not looking for any help with this, but thanks for offering. |
How is this coming along? I am a .NET developer and can definitely help get things ported to .NET 6 / 7. Once ported, the UI stack should be able to be migrated to .NET MAUI to support MacOS and Linux (Linux is community supported for .NET MAUI.). I'd love to help if you'd let me. |
Porting to .NET 7 will be done in P11. I'm currently not seeking any help with it, but thanks for the offer. We will not be changing UI stack in 11. Also we won't be using MAUI, the plan is to use Avalonia in future. |
Probably not 3.0 that should release later this year (mainly because CefSharp support is till in the air), but .NET 5 (targeted for late 2020) seems like a logical choice to me.
The text was updated successfully, but these errors were encountered: