Installation & Service Registration

Package Installation

The Furion framework already includes this feature out of the box, so no additional NuGet package installation is required. If you are not using the Furion framework, you can install the HttpAgent or HttpAgent.AspNetCore package with the following commands:

For any .NET/C# application:

dotnet add package HttpAgent

For Web applications (includes HttpAgent and provides HttpContext forwarding):

dotnet add package HttpAgent.AspNetCore

Before making HTTP remote requests, you need to register and configure the HttpRemote service in the Startup.cs or Program.cs file.

// Register in Startup.cs:services.AddHttpRemote();// In Program.cs, register as follows:// builder.Services.AddHttpRemote();

Resolving the AddHttpRemote ambiguity error

If you encounter an ambiguity error for the AddHttpRemote method, you can resolve it by adding an empty delegate parameter, as shown below:

services.AddHttpRemote(builder => {});

Then, inject the IHttpRemoteService service into your services, controllers, or any class that supports dependency injection.

123456789

public class YourService{    private readonly IHttpRemoteService _httpRemoteService;    public YourService(IHttpRemoteService httpRemoteService)    {        _httpRemoteService = httpRemoteService;    }}

If you are using .NET 8 or later, you can simplify the code by injecting via primary constructor:

public class YourService(IHttpRemoteService httpRemoteService){    // Use the httpRemoteService variable}

Alternatively, you can also inject it on demand in a specific method:

public class YourService{    public Task<string> GetResource([FromServices] IHttpRemoteService httpRemoteService)    {        // Your code logic here    }}

Usage without a dependency injection environment

In .NET Core application development, it is recommended to build applications using dependency injection. Therefore, where conditions permit, it is recommended to prefer dependency injection for managing services. However, in certain specific scenarios, such as console applications (Console), WinForms, or WPF projects, .NET does not integrate a complete dependency injection container by default. In such cases, you can use the following two approaches to manually obtain the required services:

Furion framework

If the project uses the Furion framework, you can inject the root container into HttpRemoteClient at startup. Afterwards, you can make HTTP requests through the HttpRemoteClient.Service static property:

var app = builder.Build().UseHttpRemoteClient();   // Inject the root container into HttpRemoteClient

var result = await HttpRemoteClient.Service.GetAsStringAsync("https://furion.net/");

You can also directly resolve the HTTP remote request service and send requests:

var httpRemoteService = App.GetRequiredService<IHttpRemoteService>();

Other projects (Console/WinForms/WPF)

For ordinary Console/WinForms/WPF projects, you can use the Service property provided by the HttpRemoteClient static class to make remote HTTP requests:

var result = await HttpRemoteClient.Service.GetAsStringAsync("https://furion.net/");

Usage recommendation: The above two approaches should be used as supplementary means to the dependency injection mechanism, not as a replacement. In environments that support dependency injection, please follow standard dependency injection practices to build and manage application services as much as possible.

For detailed configuration of HttpRemoteClient, custom service registration, and how to integrate an external dependency injection container with the static class, see 8.16 Using in a non-dependency-injection environment (Console/WinForms/WPF).