Refit VS Eto.Forms

A lot of people have given you good replies, but have you looked at Refit?

Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?

Define a Refit client interface with the following for each API endpoint, e.g. GET /foo:

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

Refit - simple, typed REST clients: https://github.com/reactiveui/refit

I'd advise using this https://github.com/reactiveui/refit tool for HTTP requests. It saves a lot of time for serialization, deserialization and exception handling.

Use Refit, and let manage the live of HttpClient. Also, Refit will give you a strongly typed client around an API. All you have to write is the interface. Ain't that neat ? If you can't, use the HttpClientFactory to create the HttpClient instance: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

The controller is simple and use the Refit library to abstract the PokéAPI call and then, returns the data.

To be fair, Refit is pretty great.

An option that does not seem to have been mentioned yet is Eto.Forms: https://github.com/picoe/Eto

And the above is caused by https://github.com/picoe/Eto/issues/2361

Eto Forms - Simple cross-platform UI toolkit using native components, also for F# - https://github.com/picoe/Eto

Yes, you can use Eto.Forms. There is also Windows Forms (with WYSIWYG editor).

Check out Eto Forms

Look at the Wiki: Containers

To move on to GUI dev, there's the Qt Framework, Eto.forms for C#; Rust has the ImGui wrapper for the C++ Dear ImGui library.

I've been using Eto Myself