Skip to main content

Impress your colleagues with your knowledge about … .NET Debugging Information

Sometimes when working with C# you discover some hidden gems. Some of them very useful, other ones a little bit harder to find a good way to benefit from their functionality. One of those hidden gems that I want to share today is the magic behind debugging in .NET; PDB files.

Open a project in Visual Studio, right click on it and go to Properties. Go to the Build tab and click on the Advanced… button on the bottom of the screen.

In the Debugging information you can choose between Full, Pdb-only, or Portable. But what does this mean and what is the difference? Let’s find out…

Debugging information

By configuration the Debugging information, you can choose what info is generated by the compiler to help you debug your application. It has the following options:

  • none

    Specifies that no debugging information will be generated.

  • full

    Enables attaching a debugger to the running program.

  • pdbonly

    Allows source code debugging when the program is started in the debugger but will only display assembler when the running program is attached to the debugger.

  • portable

    Produces a .PDB file, a non-platform-specific, portable symbol file that provides other tools, especially debuggers, information about what is in the main executable file and how it was produced. This is the most recent cross-platform format for .NET Core.

  • embedded

    Embeds portable symbol information into the assembly. No external .PDB file is produced.

Which one should I choose?

If you use full, be aware that there is some impact on the speed and size of JIT optimized code and a small impact on code quality with full. For development purposes you want the full debugging experience so full will be the logical choice. pdbonly or none is recommended for generating release code.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...