Issues with finding usages of a member implementing an interface member

[nvmkpk]

When a member is implementing an interface member, often we run into cases where it is only invoked via the interface member (very common in asp.net core). In this case ILSpy does not find any usages of it and requires us to analyze the interface member to find its possible usages. I would like to see an additional option under the member for Implements that would list the interface member it is implementing (or list it under Exposed By if it makes sense). That would make it little easier to find the usages.

[siegfriedpammer]

Possible duplicate of #648

[nvmkpk]

Yes, I created new one because that issue is closed and I included a suggestion for better implementation/fix than the workaround mentioned there.

[nvmkpk]

It is nice to see this implementation. Would have been even nicer if overridden members are also shown under 'Overrides' (if not under 'Implements').