How to use DebuggerTypeProxy while debugging your sensitive Type

Debugger in .NET runs in background on each and every type and uses Reflection to load the information regarding the Type that is running on the code. It is not generally great to view the entire object state as many of the intermediate states are not necessary to any user of your code.  Hence if you are building a library, it is your duty to enhance the Debugging experience of the application developer annotating Debugging attributes on your code. We use DebuggerHidden to hide something from the debugger, or DebuggerStepThrough to step through some code while debugging. But when you have built a complex type yourself, and not want to show what is inside of it in Debugger, you can use DebuggerTypeProxy class to create a proxy of the class which is been used and show only the portion which is important.

DebuggerTypeProxy is used to enhance the debugging experience of the user by providing a new class for the existing one allowing you to rearrange the important properties from it in Watch window rather than dealing with the pain of finding it out in the hierarchy of the type.  The most simplest example is when you want to deal with IEnumerables. It is really hard to get information of an IEnumerable. Lets add a Proxy to see how we can improve the debugging experience of the user using DebuggerTypeProxy attribute.

Say we define a class MyType which lists some string like this :

public class MyType
public List Items { get; set; }

public MyType()
this.Items = this.Items ?? new List();


Here the class lists a collection of string in itself. It is better to use a comma separated string for the same rather than viewing the same thing in hierarchy. Lets do it now.

public class MyProxyClass
public MyType BaseType { get; set; }

public MyProxyClass(MyType basetype)
this.BaseType = basetype;

public string Items
return string.Join(",", this.BaseType.Items);

Notice the Proxy class takes the original class (in this case it is MyType) in constructor argument. Now we expose the Items here as string rather than a collection.

If we try to run our code we see something like this :

So you can see, rather than seeing the actual Items property, we see the new property from the proxy class.

You can download the sample application

Read More from here.

I hope this would help you.

Thanks 🙂

Abhishek Sur

Abhishek Sur is a Microsoft MVP since year 2011. He is an architect in the .NET platform. He has profound theoretical insight and years of hands on experience in different .NET products and languages. He leads the Microsoft User Group in Kolkata named KolkataGeeks, and regularly organizes events and seminars in various places for spreading .NET awareness. He is associated with the Microsoft Insider list on WPF and C#, and is in constant touch with product group teams. He blogs at His Book : Visual Studio 2012 and .NET 4.5 Expert Development Cookbook. Follow Abhishek at Twitter : @abhi2434

One Comment to “How to use DebuggerTypeProxy while debugging your sensitive Type”

Comments are closed.