I suggest you ...

Revisit CodeLens user option to display above attributes

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/351553/revisit-codelens-user-option-to-display-above-attr.html
Suggestions to CodeLens have been getting shot down repeatedly before it can gather the support needed. I feel that requests should not be marked DECLINED as then we can no longer vote on the issue. Nobody that I work with even knew this was call CodeLens until we looked it up.

The example provided in previous declined messages (with the massive block of attributes) is valid but those are an exception and not the rule. And in my personal opinion, stylistically, CodeLens looks like a separator and breaks the flow between attributes and declarations in a horrible way, regardless of the distance from the declaration. I would even prefer it after the declaration and before the implementation, if you need it to remain close. It should be the user's choice.

And in my world, having 30+ "[XmlElement] string Property { get; set; }" lines in a class and is far more common and CodeLens makes it muddy.

[XmlElement]
-codelens-
public string Property { get; set; }
[XmlElement]
-codelens-
public string Property { get; set; }
[XmlElement]
-codelens-
public string Property { get; set; }

Interest outside of voice:
707 views: https://stackoverflow.com/questions/22447557
673 view: https://stackoverflow.com/questions/20389267

75 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Josh Brown shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base