Not sure what you’re referring to. It’s not about CPU usage, it’s about getting it to work on multiple platforms and .Net Framework isn’t the way nor is WinForms or MAUI, nor is http.sys. It’s also about architecting it to be doable with managable chunks of effort and long term future.
- gRPC is the recommended way (even by Microsoft) for remoting after they killed off their WCF and Remoting, see here Why we recommend gRPC for WCF developers - gRPC for WCF developers - .NET | Microsoft Learn and here Overview for gRPC on .NET | Microsoft Learn and gRPC + ASP.NET Core as a Migration Path for WCFs in .NET Core - Developer Support and What's new for gRPC in .NET 6 - .NET Blog
- Avalonia is the way for cross platform desktop apps continuing on from WPF XAML
- .Net is the way for managed cross platform applications, not .Net Framework
- Daemon is a way to separate out the character data from the UI and make it more mangable to port (long term) and mix into .Net managed HttpListener without http.sys and cross the Wine/Native boundary (fix to get OAuth2 SSO working)
- You cannot use HttpListener in Wine on Linux/MacOS due to http.sys so you have to cross the boundary via remoting to call the one without http.sys in .Net 6 natively, if you cannot SSO, you effectively have no app.
The only alternative is to rewrite it in one big effort, good luck. An “upgrade wizard/assistant” won’t fix it for you.