Why EditorBrowsable doesn't work?

Question

I tried to hide inherited property in intellisense with EditorBrowsable (as said here Hiding user control properties from IntelliSense), when testing in client form though I can still see it why ?

[
Category("Main"),
Description("Text"),
Obsolete("Don't use this"),
Browsable(false),
EditorBrowsable(EditorBrowsableState.Never)
]
public override String Text
{
    get { return null; }
}

Few years passed, but for anyone interested: https://github.com/dotnet/roslyn/issues/4434 — quetzalcoatl, Feb 18 '18 at 13:30

score 45 · Answer 1 · edited Apr 28 '21 at 06:34

45

Are you using ReSharper? It seems like ReSharper doesn't obey the EditorBrowsable attribute.
If I turn off ReSharper, I don't see my property. If I turn ReSharper on, it does show.

In ReSharper Options, go to Environment | IntelliSense | Completion Appearance and check "Filter members by [EditorBrowsable] attribute".

You still have to reference the assembly though, it doesn't work within a solution if you reference your usercontrol's project.

edited Apr 28 '21 at 06:34

Pang

9,564
146
81
122

answered Dec 14 '10 at 16:50

comecme

6,086
10
39
67

1

No I'm not using Reshaper. I have opened the client project in another solution and point to the dll from toolbox and I can still see Text property in intellisense. I think I'll give up seems too irational for me :) – user310291 Dec 14 '10 at 22:41
that worked for me, as I am using resharper. Even with the same solution when referenced as a project it works. thank you! – afif Apr 22 '12 at 12:45
Thanks! After hours trying to make it work, I read your answer and voilá! Works flawlessly now. Thanks, I'd never thought resharp was causing it. – Retired_User Jan 29 '13 at 23:30
To me it seems like Resharper can actually enforce obeying of this attribute where VS does not. If I disable Resharper, the attribute does not work - only when I enable Resharper and set this filtering, then it works. Verified in 2015 and 2017. – Bartosz Dec 17 '18 at 09:23

score 27 · Accepted Answer · edited Apr 30 '17 at 14:49

27

I repro. There is a Note in the MSDN article about this:

In Visual C#, EditorBrowsableAttribute does not suppress members from a class in the same assembly.

Oddly, I don't see it suppress it either when I put the UserControl in a different assembly in the same solution.
You may want to ping connect.microsoft.com about this, something isn't right.

edited Apr 30 '17 at 14:49

Hakan Fıstık

16,800
14
110
131

answered Dec 14 '10 at 16:45

Hans Passant

922,412
146
1,693
2,536

did you close and reopen VS? VS caches controls. – Dec 14 '10 at 17:43
at least you seem to have same result as me so i'm not crazy :) Will give up too irational for me ! – user310291 Dec 14 '10 at 22:42
4

Few years passed, but for anyone interested: https://github.com/dotnet/roslyn/issues/4434 – quetzalcoatl Feb 18 '18 at 13:30

score 15 · Answer 3 · edited May 23 '17 at 12:26

15

As said in this answer's comments:

editorbrowsable only hides the method if you're just importing the dll, not if you're referencing another project in the solution i think

edited May 23 '17 at 12:26

Community

1
1

answered Aug 22 '14 at 21:50

Jerther

5,558
8
40
59

score -2 · Answer 4 · answered Oct 17 '18 at 14:41

-2

Have you tried this:

Visual Studio > Tools > Options > General > Hide Advance Members

Check the "Hide Advance Members", remember that, in Visual C#, EditorBrowsableAttribute does not suppress members from a class in the same assembly.

EditorBrowsableAttribute Class

answered Oct 17 '18 at 14:41

Pl4tinum

123
15

this solution not working for me in VS2019 – mrbm Dec 16 '20 at 22:18

Why EditorBrowsable doesn't work?

4 Answers4