Operations | Monitoring | ITSM | DevOps | Cloud

ADO.NET Tutorial: A Comprehensive Guide for Beginners and Professionals

Long before ORMs, LINQ, and high-level abstractions became common in the.NET ecosystem, there was ADO.NET—raw, fast, and unapologetically hands-on. It was the original data access layer for developers who wanted complete control. And two decades later, it’s still the tool of choice when performance, precision, and transparency matter most. But how does it deliver that control?

.NET Logging with Serilog and OpenTelemetry

Debugging modern.NET apps isn’t as simple as scanning logs anymore. With services spread out and systems growing more complex, it's easy to miss the bigger picture. Serilog gives you clean, structured logs. OpenTelemetry brings in traces and metrics to connect the dots. This guide covers how to wire up Serilog with OpenTelemetry, send logs to traces, and build an observability setup that helps you troubleshoot, without digging through disconnected logs for hours.

NHibernate vs. Dapper: Which One Should You Choose for .NET Development?

Frameworks evolve, libraries change, and APIs get rewritten. But your ORM decision? That one sticks—it shapes your architecture, guides how your team writes queries, and affects how painful refactors become later on. In.NET, this choice often narrows to Dapper and NHibernate—two trusted tools with fundamentally different approaches. NHibernate offers deep abstraction, rich mappings, and built-in caching, while Dapper gives you raw speed, total SQL control, and zero overhead.

ADO.NET vs Dapper: Comparison Guide for .NET Developers

In.NET, data access has evolved, but finding the right tool still comes down to control vs. convenience. You have to decide: do you prefer to write every query or move faster with something easier to maintain? Can you manage the boilerplate, or would you rather work with leaner syntax? For many.NET developers, the answers point to one of two popular tools—ADO.NET or Dapper. ADO.NET gives you complete control but with boilerplate and manual overhead.

Understanding GraphQL in .NET: When and why to use it

APIs are the heart of most modern applications. Due to their simplicity and lightweight design, RESTful APIs are a popular choice for client-server communication in most applications. However, APIs can become limiting when fetching complex or related data. The front end may over-fetch or under-fetch the meaningful data. For example, different pages require different responses. RESTFul APIs require different field endpoints, each involving repetitive complex joining conditions.
Sponsored Post

Top 10 .NET exceptions (part two)

In Part 1, we walked through the top 5 most common.NET exceptions-breaking down what triggers them and how to fix them. Now, we're rounding out the list with five more exceptions every.NET developer is bound to encounter at some point: These exceptions can stem from database issues, memory mismanagement, and logic errors that can bring your applications to a halt. In this article, we'll break down each one, explain when and why they occur, and share practical strategies to fix them so you can keep your code running smoothly.

Dapper vs. Entity Framework Core: Which One Is Right for Your .NET Project?

“Dapper is pure speed—EF Core is bloated,” or “Dapper is a nightmare—EF Core keeps things scalable.” We’ve all heard it. Both sides make a point, but neither tells the whole story. The real question? Which one will save you from a world of pain six months from now? Dapper gives you raw SQL execution and total control, but you’re on your own when managing transactions, relationships, and migrations.

Relationships in Entity Framework Core: Complete Guide for .NET Developers

Entity Framework Core (EF Core) is a modern object-relational mapper (ORM) for.NET Core and.NET applications, enabling efficient database interaction while minimizing the need for raw SQL queries. A fundamental aspect of EF Core is defining Entity Framework relationships, ensuring data consistency and referential integrity in relational databases. This guide explores one-to-one, one-to-many, and many-to-many relationships in EF Core, covering their implementation, configuration, and best practices.

Debugging a .NET Application with Loggly

As modern applications grow more complex, debugging becomes increasingly challenging. Applications consist of multiple parts which can generate enormous amounts of log data, making debugging difficult. SolarWinds Loggly can help store, manage, and sift through this data. To demonstrate, we’ll set up an application built on.NET Core 9.0 and MongoDB; then, we’ll walk through how to export its logs to Loggly.