Top 10 popular external libraries used in dotnet

Here are the Top 10 most popular and widely used third-party .NET libraries, along with what they’re used for and short code examples.

---

⚙️ 1. Newtonsoft.Json (Json.NET)

👉 Most popular library for JSON serialization / deserialization.

using Newtonsoft.Json;

var person = new { Name = "Sagar", Age = 30 };
string json = JsonConvert.SerializeObject(person);
var obj = JsonConvert.DeserializeObject<dynamic>(json);

Console.WriteLine(obj.Name); // Sagar

💡 Still widely used even though .NET Core/5+ includes System.Text.Json.

---

🧠 2. AutoMapper

👉 Automatically maps properties between different objects (DTO ↔ Entity).

var config = new MapperConfiguration(cfg => cfg.CreateMap<User, UserDto>());
var mapper = config.CreateMapper();

UserDto dto = mapper.Map<UserDto>(new User { Name = "Sagar" });

💡 Reduces boilerplate when converting between layers.

---

🔗 3. Serilog

👉 Structured, pluggable logging framework.

using Serilog;

Log.Logger = new LoggerConfiguration()
    .WriteTo.Console()
    .WriteTo.File("log.txt")
    .CreateLogger();

Log.Information("App started");

💡 Supports sinks for console, file, Seq, Elasticsearch, etc.

---

💾 4. Dapper

👉 Lightweight micro-ORM (faster alternative to Entity Framework).

using Dapper;
using (var conn = new SqlConnection(connString))
{
    var users = conn.Query<User>("SELECT * FROM Users").ToList();
}

💡 Ideal for performance-critical data access.

---

🌐 5. RestSharp

👉 Simplifies making HTTP API calls.

var client = new RestClient("https://api.example.com");
var request = new RestRequest("users/1", Method.Get);
var response = client.Execute(request);
Console.WriteLine(response.Content);

💡 Great for testing or consuming REST APIs.

---

🧪 6. NUnit / xUnit

👉 Testing frameworks used for unit and integration tests.

[Test]
public void Add_TwoNumbers_ReturnsSum()
{
    Assert.AreEqual(4, Calculator.Add(2, 2));
}

💡 xUnit is preferred in .NET Core; NUnit still widely used in legacy projects.

---

🔐 7. FluentValidation

👉 Expressive validation for models.

public class UserValidator : AbstractValidator<User>
{
    public UserValidator()
    {
        RuleFor(x => x.Email).NotEmpty().EmailAddress();
        RuleFor(x => x.Age).InclusiveBetween(18, 60);
    }
}

💡 Integrates with ASP.NET Core model validation.

---

📦 8. Polly

👉 Handles resilience & transient-fault policies like retry, circuit-breaker, fallback.

var policy = Policy
    .Handle<HttpRequestException>()
    .Retry(3);

policy.Execute(() => CallExternalService());

💡 Common in microservices and API clients.

---

🧩 9. MediatR

👉 Implements the Mediator pattern — decouples request/response handling.

public record GetUserQuery(int Id) : IRequest<User>;

public class GetUserHandler : IRequestHandler<GetUserQuery, User>
{
    public Task<User> Handle(GetUserQuery request, CancellationToken token)
        => repository.GetUserAsync(request.Id);
}

💡 Keeps controllers clean in CQRS architecture.

---

🧰 10. Hangfire

👉 Background job processing framework for .NET.

BackgroundJob.Enqueue(() => Console.WriteLine("Hello from background job!"));

💡 Supports delayed, recurring, and distributed jobs with dashboard.

---

🧩 Bonus popular libraries

Library	Purpose
Entity Framework Core	ORM (official, but often paired with third-party providers)
NLog / log4net	Alternative logging frameworks
Quartz.NET	Advanced job scheduling
ClosedXML / EPPlus	Excel file manipulation
MailKit / MimeKit	Sending and parsing emails
Bogus	Generate fake test data

---

💬 Interview Tips

✅ Know why you’d choose each library:

• Dapper → speed.
• AutoMapper → cleaner code.
• Polly → resilience.
• MediatR → CQRS architecture.
• Serilog → structured logging.

✅ Be ready to discuss trade-offs — e.g., why use System.Text.Json vs. Newtonsoft.Json.