Attribute signature is not correct

[mairaw]

This is an issue brought up by @riverar on MicrosoftDocs/feedback#298 (comment)

Type: https://docs.microsoft.com/en-us/dotnet/api/accessibility.caccpropservicesclass

According to the docs, there is no parameter-less constructor for ClassInterfaceAttribute.

mdoc is generating this:

<Attribute FrameworkAlternate="netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8">
      <AttributeName>System.Runtime.InteropServices.ClassInterface</AttributeName>
</Attribute>

Source shows those monikers actually use the constructor with the ClassInterfaceType parameter:

[ClassInterface(ClassInterfaceType.None)]

[joelmartinez]

@mairaw This source has since been changed to:

    <Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5">
      <AttributeName>System.Runtime.InteropServices.ClassInterface(0)</AttributeName>
    </Attribute>

So it's no longer showing as using an empty constructor ... is the value 0 correct, though?

[riverar]

Hey @joelmartinez, that looks correct. 0 corresponds to ClassInterfaceType.None. The docs now show duplicate values, though:

[System.Runtime.InteropServices.ClassInterface(0)]
[System.Runtime.InteropServices.ClassInterface(System.Runtime.InteropServices.ClassInterfaceType.None)]

Source: https://referencesource.microsoft.com/#Accessibility/Accessibility/CAccPropServicesClass.cs,10

[joelmartinez]

@riverar awesome, thanks for looking that up :) So it's "correct" now, but for some reason that enum value lookup didn't work (that's the only reason for the 'duplicate'). I'll leave this item open so we can investigate that and get it rendering with 100% fidelity :)

[mairaw]

Thanks for your help validating that @riverar!

[mimisasouvanh]

Internal bug logged.