Create a sample enum, like:

using System; using System.Runtime.Serialization;

namespace TestNamespace { /// <summary> /// Test enumeration. /// </summary> public enum TestEnum { /// <summary> /// First member. /// </summary> MemberOne,

/// <summary>
/// Second member.
/// </summary>
[EnumMember]
MemberTwo

}

Look at the class doc for the enumeration. In the table that lists the members, the member without the attribute ("MemberOne") will have its description correctly listed; the member with the attribute ("MemberTwo") will not.

Both should have a proper description.

Fixed the TransformEngine base/abstract class "RenderElementSummary" method. Previously it would get the element node that was documented (the enum member), then grab the previous node (usually the XML doc, but sometimes an attribute) and try to render that. The new implementation determines if the element node (the enum member) even has documentation and, if so, walks backwards up the parse tree until it finds it or can't walk backwards anymore.

Just found an issue with the way I fixed it - now enum members that don't have any documentation get the documentation of the previous enum member.

OK, fixed "for reals" this time. Converting member elements to CodeElement. If it can't be documented (!CodeElement.CanBeDocumented) or isn't a code element, we don't render summary info. If it can be documented, we get the CodeElement.DocComment for the element. If it exists, render. If not, skip it.