Why are the names of generic types mangled in a .NET stack trace?

The reason why is that the stack trace is generated by the CLR and not C#. Hence it uses CLR type names vs. C# type names.

The reason why is that the stack trace is generated by the CLR and not C#. Hence it uses CLR type names vs. C# type names. The type names given to generic types in metadata (in both C# and VB.Net) have the form TypeName`Number where TypeName: Name of the type in the abscence of generic parameters Number: Count of generic parameters on the type This is also why it's legal to have several generic classes which the same name but differing numbers of generic parameters.

At a CLR level they have different type names.

Jared, heh, we both added the extra details at the same time. :o – 280Z28 Sep 2 '09 at 18:19.

Look for the "`" to show you a reference back to the type called in your code. It takes some practice but it is possible. -Shaun.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.