ReSharper Support | JetBrains

Richard Deeming

Total activity 637
Last activity July 31, 2026 10:47
Member since October 06, 2010 20:13
Following 0 users
Followed by 0 users
Votes 47
Subscriptions 218

Created May 28, 2020 08:49

If you look at the screen-shots further up the article you linked to, the refresh button appears for the "code inspection results", but not the "call tracking" or "value tracking" results. I have n...
- 0 votes
Created May 27, 2020 09:44

Are the properties set anywhere else in the code? If not, R# is correct - removing the setter won't cause any errors. The property initializer syntax is equivalent to setting the property in the co...
- 0 votes
Created May 06, 2020 11:21

The other option would be to fully-qualify the enum type name: <see cref="YourNamespace.IconType.WellKnownIcon" />
- 0 votes
Created May 06, 2020 09:49

I suspect it's getting confused between the enum type and the property of the same name. Try prefixing the reference with the member type identifier: <see cref="F:IconType.WellKnownIcon" />. https:...
- 0 votes
Created February 13, 2020 11:02

Try adding [InstantHandle] to your func parameter. public static T FirstOrDefault<T>([NotNull] this IReadOnlyList<T> list, [NotNull, InstantHandle] Func<T, bool> func) However, I'd be surprised if ...
- 0 votes
Created February 13, 2020 10:54

Have you tried deleting the _ReSharper.Caches folder from your project (with VS closed, obviously)? That usually fixes it for me.
- 0 votes
Created February 05, 2020 11:06

My guess would be that either there's a firewall getting in the way, or you don't have TLS 1.2 enabled in your client protocols. How to enable Transport Layer Security (TLS) 1.2 on clients - Config...
- 0 votes
Created January 27, 2020 09:44

ReSharper has its own "heap allocations viewer" plugin which might help: https://plugins.jetbrains.com/plugin/9223-heap-allocations-viewer
- 0 votes
Created December 12, 2019 10:53

Thanks.
- 0 votes
Created December 11, 2019 16:03

I've just tried the final release of 2019.3; I didn't get around to testing whether it fixes this problem, because the intellisense / autocomplete is so badly broken I had to roll back.
- 0 votes