You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed for a while now that letting an interface inherit from IFluentInterface no longer appears to result in System.Object members being hidden in IntelliSense in recent versions of Visual Studio.
For example, here's a screenshot of a solution in Visual Studio Community 2017 (version 15.5.2) using Moq (which gets imported in the standard fashion, i. e. as a NuGet package):
My IntelliSense options are as follows:
Visual Studio's support for [EditorBrowsable] isn't generally broken—other members are still properly hidden, e. g.:
Moq.Mock.Expect (method marked with EditorBrowsableState.Never)
Moq.Internals.InterfaceProxy (type marked with EditorBrowsableState.Never)
Moq.LookupOrFallbackDefaultValueProvider (type marked with EditorBrowsableState.Advanced)
Can you confirm that this is a problem with current versions of Visual Studio?
The text was updated successfully, but these errors were encountered:
TL;DR: This is likely caused by a Roslyn bug; see dotnet/roslyn#4434.
I've noticed for a while now that letting an interface inherit from
IFluentInterface
no longer appears to result inSystem.Object
members being hidden in IntelliSense in recent versions of Visual Studio.For example, here's a screenshot of a solution in Visual Studio Community 2017 (version 15.5.2) using Moq (which gets imported in the standard fashion, i. e. as a NuGet package):
My IntelliSense options are as follows:
Visual Studio's support for
[EditorBrowsable]
isn't generally broken—other members are still properly hidden, e. g.:Moq.Mock.Expect
(method marked withEditorBrowsableState.Never
)Moq.Internals.InterfaceProxy
(type marked withEditorBrowsableState.Never
)Moq.LookupOrFallbackDefaultValueProvider
(type marked withEditorBrowsableState.Advanced
)Can you confirm that this is a problem with current versions of Visual Studio?
The text was updated successfully, but these errors were encountered: