why the JsonServiceClient not use HttpClient?

[1257960069]

from source code of AsyncServiceClient.I found it
#if NET6_0_OR_GREATER
public System.Net.Http.HttpClient HttpClient { get; set; }
#endif

but it just use the extensions method (var webReq = this.CreateHttpWebRequest(requestUri)) at method SendWebRequestAsync
it seems that HttpClient is not usefull, the usefull system http class is HttpWebRequest.

how to control JsonServiceClient's Httpclient lifetime?

[mythz]

The newest C# ServiceClient that uses HttpClient you should use is the JsonApiClient which for .NET 6+ is included in the ServiceStack.Client NuGet package, see:

https://docs.servicestack.net/csharp-client#jsonapiclient

var client = new JsonApiClient(baseUri);

Which can also be registered in your App's IOC using the HttpClient factory:

builder.Services.AddJsonApiClient(builder.Configuration["BaseUrl"]);

Which supports both Async and Sync APIs.

The older JsonServiceClient is for legacy clients which uses .NET Framework's older HttpWebRequest implementation.

[1257960069]

use constructor injection,but not dispose yet at request end.
I think this could lead to memory leaks, and if each service needs to be manually disposing, it would lose the convenience of automatic disposing through dependency injection

[mythz]

Since you prefer to use ASP.NET Core IOC you can make use of our new Endpoint Routing and IOC feature which makes use of ASP.NET Core's IOC for registering and resolving Services and ASP.NET Core Endpoint Routing for calling them.

What template is your project based on? I'll convert it to use the new Endpoint Routing support now available in our pre-release packages

[1257960069]

I use command "x new web MyWeb" to create the template

[mythz]

ok I've got an updated project which you can create with:

x new mythz/web MyWeb

It uses ASP.NET Core's IOC for all dependencies (inc. Services), uses Endpoint Routing and System.Text.Json by default.
I've also configured it with ASP.NET Core's Swagger UI so you can see that ServiceStack Services now integrates with other ASP.NET Core Minimal APIs, controllers etc which also use endpoint routing.

We're currently working on the docs now, but should be hopefully ready for release by next week.

[1257960069]

Thank you for your immediate feedback. asp.net core servicecollection can not support property in the past, but now can work at property,however,it need a attribute named [FromService].