RestClient.Net
RestSharp
Our great sponsors
RestClient.Net | RestSharp | |
---|---|---|
11 | 13 | |
360 | 9,419 | |
- | 0.6% | |
5.2 | 6.0 | |
12 months ago | 10 days ago | |
C# | C# | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RestClient.Net
- What's the deal with HttpClient?
-
RestClient.Net 5.0.x Beta Released
RestClient .Net is completely immutable and therefore much more thread-safe. It also works well with standard Microsoft dependency injection, and it's easy to mock. Have a look at the abstraction. If you use this, it's a one-step process for mocking HTTP calls.
https://github.com/MelbourneDeveloper/RestClient.Net/blob/e7edf5c1b40305732af3b0bd10c548996889ba97/src/RestClient.Net.Abstractions/IClient.cs#L9
RestSharp
-
Building a Gateway to Netflix API: A Developer's Guide
RestSharp
-
ASP.NET Core - how to properly make a GET request?
Use RestSharp to create a client library. It requires you to write more code, but it's still a lot less boilerplate than using HttpClient directly.
- static HttpClient inside a using statement?
-
Benchmarks Clients Http
RestSharp:
-
Send postcards with C# and Flurl
On line 16, we append the endpoint that we are going to connect to. In this example, we hit the “/addresses” endpoint. On line 17, we authenticate to Lob using Basic Authentication. Our Lob API key is placed where the username would be and we leave the password empty. Flurl sets the basic-auth headers using the WithBasicAuth method. For those using RestSharp it looks like this.
- RestClient.Net 5.0.x Beta Released
-
Transitioning from WCF
This is going to be a pain because adding a service reference handles a lot of the "plumbing" in terms of making your API calls. I suggest you use something like RestSharp to make things easier to make the calls themselves, and potentially look at some code generation for generating similar proxy classes to what service references did. In fact, it should just be partials behind the scene, so maybe making a copy and seeing if you can rip out the WCF guts and replacing them with REST ones might be worth exploring.
What are some alternatives?
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
RestEase - Easy-to-use typesafe REST API client library for .NET Standard 1.1 and .NET Framework 4.5 and higher, which is simple and customisable. Inspired by Refit
Ocelot - .NET API Gateway
Simple.OData.Client
EasyHttp - Http Library for C#
Tiny.RestClient - Simpliest Fluent REST client for .NET
WebApiClient - An open source project based on the HttpClient. You only need to define the c# interface and modify the related features to invoke the client library of the remote http interface asynchronously.
Sandwych.JsonRpc - Sandwych.JsonRpc: A JSON-RPC Client For .NET
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
mockhttp - Testing layer for Microsoft's HttpClient library. Create canned responses using a fluent API.
Lib.Net.Http.WebPush - Lib.Net.Http.WebPush is a library which provides a Web Push Protocol based client for Push Service.