If you’ve been writing code for any reasonable amount of time, then it’s virtually impossible that you haven’t handled logging in any way, since it’s one of the most essential parts of modern, “real life” app development. If you’re a .NET developer, then you’ve probably used some of the many famous logging frameworks available for use at this platform. Today’s post will cover one of these frameworks: log4net.

Collecting observability data like metrics, traces, and logs makes it much easier to identify bottlenecks and other performance problems in your .NET applications. When you need to troubleshoot a production incident, it’s especially important to be able to navigate all that data so you can find the source of the issue and enact a timely resolution.

Debugging. It’s one of the most time-consuming ways of finding a bug. As a senior .NET developer, I can tell you that it’s best to avoid the necessity for debugging altogether by writing clean code that’s covered by automated tests. If you’re a senior developer yourself, you probably already know this. And if you’re a junior developer, now you know it too! However, the world isn’t binary.

Since it was first introduced in 2002, Microsoft’s .NET Framework has garnered a robust user base that includes organizations like UPS, Stack Overflow, and Jet.com. And now, thanks to the rise of the .NET Core runtime, this high-performance framework also supports cross-platform development. To provide deeper visibility into all of these environments, we are pleased to announce that Datadog APM and distributed tracing are generally available for .NET Framework and .NET Core applications.

Working in C#, as with any language, you’ll soon find that that you need to do some debugging. With C#, thankfully, due to a plethora of debugging tools and techniques, troubleshooting is usually straightforward.

At some point in our careers, many of us have found ourselves working on a project that requires performance tuning. The need to write high performance .NET code should come from performance issues or business needs. Today, we’ll take a look at just a few of the ways we can improve our .NET application’s performance. And hopefully, you’ll take away something that you can use on your current and future products.

Raygun’s Launch Notes are your regular roundup of all the improvements we made to Raygun last month—from major features to performance updates.