开发者

Is there a standard/common practice for documenting an event handler? [closed]

开发者 https://www.devze.com 2023-03-10 03:49 出处:网络
Closed. This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be开发者_C百科 answered with facts and citations b
Closed. This question is opinion-based. It is not currently accepting answers.

Want to improve this question? Update the question so it can be开发者_C百科 answered with facts and citations by editing this post.

Closed 5 years ago.

Improve this question

This is something that causes me some pause from time to time. It seems like I need to provide a description for sender and e. Since I cannot think of anything particularly meaningful I'd prefer to delete the two param elements.

    /// <summary>
    /// Fired when the destination project is updated.
    /// </summary>
    /// <param name="sender"></param>
    /// <param name="e"></param>
    private void UpdateDestinations(object sender, EventArgs e)


You might want to use GhostDoc to do all the heavy lifting for you (like the parameters documentation for example) so that you can concentrate on providing meaningful information for the remaining elements (the summary in that case).

0

精彩评论

暂无评论...
验证码 换一张
取 消