Yes this is correct. These two methods have different goals.
Comments /// <summary></summary> are used to create XML documentation for your project at compile time, which Visual Studio also parses for its IntelliSense database.
[DescriptionAttribute] contains the description text that is used in the designer, especially at the bottom of the properties window.
In Microsoft Windows Forms, the library is littered with both of these.
I don’t know how to merge these two, but think about whether you really want them to be exactly the same. In my own class libraries, I often want to display a little bit of information in the designer than I want to include in my technical documentation.
As a simple example, I could make it clear in the designer that this property is not supported in certain versions of Windows, but cancel this information in the <remarks> section in my technical documents:
/// <summary> /// Gets or sets a value indicating whether a shield should be displayed /// on this control to indicate that process elevation is required. /// </summary> /// <remarks> /// The elevation-required shield is only supported under Windows Vista /// and later. The value of this property will be ignored under earlier /// operating systems. /// </remarks> [Category("Appearance")] [Description("Displays a shield to indicate that elevation is required. " + "(Only applies under Windows Vista and later.)")] public bool ShowShield { get; set; }