#14 Format of Nested Classes

[Shaun Wilde]

Nested class have an unexpected format in the partcover results but do not appear to affect the coverage display

i.e.

namespace Z
{
public class X
{
public class Y<T>
{
}
}
}

Z.XY`1

i.e. no discriminator between the class and the nested class if you look at the IL (ildasm) then it will display as

Z.X/Y`1

which is a format that people may be expecting

[Shaun Wilde]

As it does not affect coverage results (at this moment) I have marked it as low priority.

[Shaun Wilde]

also reported in 3034423

If your code contains inner classes, the Type[@name] attribute in the coverage report runs the names of the containing and inner classes together with no punctuation between (rather than separating the tokens e.g. with a + as per FxCop or / as per Mono.Cecil
The lack of separator makes a potential ambiguity in reports -- does AHoldsB refer to AHolds+B or A+HoldsB if both are present in the same assembly? Where code is compiler generated (e.g. default constructors) or just not covered, resolution by source file and line information would be thwarted.