• C# Digest
  • Posts
  • Understanding .NET stack traces

Understanding .NET stack traces

Detailed information about the error and the call stack

Understanding .NET stack traces
13 minutes by Thomas Ardal

Stack traces are important for debugging and understanding exceptions in .NET applications. They provide detailed information about the error and the call stack when an exception occurs, allowing us as developers to investigate why an error happened.

Transform your C# skills into cross-platform power with Uno Platform. Write once, run on Web, Mobile, and Desktop—all with a single codebase. No need to learn new languages; leverage your existing expertise in C# and XAML. Explore our docs and get started today.

Avoiding OverflowException when using arithmetic operations. The other day, I played around with the Fibonacci sequence and overflowed my int variables in surprisingly low iterations. Did you know you’ll overflow an integer in 48 iterations? Don’t believe me? Let’s take a look at the result of the code you’ll see later in this post.

BinaryFormatter removed from .NET 9
5 minutes by Immo Landwerth

Starting with .NET 9, there isn't an implementation of BinaryFormatter in the runtime. This post covers what options you have to move forward.

Working With DTO Auto Translators
6 minutes by Peter Ritchie

Modern software applications heavily rely on external services, making data transfer a crucial aspect of application functionality. Translation from one syntax to another must first map source data elements to target data elements. That mapping includes the necessary conversion method.

With HashSet, you can get a list of different items in a performant way. What if you need a custom way to define when two objects are equal?

how did you like this issue?

Login or Subscribe to participate in polls.

newsletters

Would you like to become a sponsor and advertise in one of the issues? Check out our media kit and get in touch.