Latest

Demystifying Memory Profilers in C# .NET Part 2: Memory Leaks

Memory leaks are very common, hard to notice, and eventually, lead to devastating consequences. The main tool to detect and fix memory leaks is a Memory Profiler. In fact, I believe the most common usage of memory profilers in .NET is exactly for the purpose of fixing memory leaks. In this article, you’ll see exactly how to use memory profilers to find the leaky objects, why they are still referenced, and how to solve the problem.

Demystifying Memory Profilers in C# .NET Part 1: The Principles

Memory leaks and GC Pressure cause pretty inconvenient effects like out-of-memory crashes, performance problems, and high memory consumption. Our primary tools when dealing with those issues are memory profilers. They are one of the most important category of tools in .NET troubleshooting, and in this article, you’ll see how to use them and extract the most information from them.

Is C# Slower Than C++?

Is C# slower than C++? That’s a pretty big question. As a junior developer, I was sure that the answer is “Yes, definitely”. Now that I’m more experienced, I know that this question is not obvious and even quite complicated.

Debugging ASP.NET Web Request Failures: The Complete Guide

You’re sending an HTTP request to your ASP.NET server, and out of the blue, it returns a 500 error. Now what? The error code doesn’t say too much by itself. Did a database request fail? Was there an exception? In this article we’ll see how to get the most information on the error.

Debugging 3rd Party .NET Code without symbols in Visual Studio

It’s not so rare to see weird things happen in 3rd party library code. Call some method and you’ve got a strange exception. Or an incorrect behavior or even a process crash. It sure would be nice to debug some of these issues. In this article we’re going to do just that – You’ll see how to debug 3rd party library code in Visual Studio.

OzCode Review and Black Friday 2019 Discount

You might have heard about OzCode before. It’s an extension for Visual Studio. Like ReSharper, but with very different functionality. The single purpose of OzCode is to help you debug code and find the root cause of problems. In this blog post, I’m going to tell you about some amazing features in OzCode from my perspective and why you should try it out.

Loading

SUBSCRIBE

Join the mailing list and get updates on new articles

Avatar

Welcome to my blog! I’m a software developer, C# enthusiast, soon-to-be author, and a blogger. I write about C#, .NET, memory management, performance, and solving difficult problems in .NET.
More about me →


On my day job, I work on OzCode, a VS extension that makes debugging C# easier.
See for yourself →

Avatar

Categories