Known issue with expression bodies in properties?

Question

I'm facing a problem with the latest ReSharper version using Visual Studio 2017 RC.

The Editor of ReSharper tells me it can't resolve symbols like var or tokens like public or void are not expected etc. pp.

Not sure but it turns out that expression bodies used in properties are the root cause.

Example:

public double PlayingProgress
{
    get => _playingProgress;
    set => SetProperty(ref _playingProgress, value);
}

If using normal brackets instead of the expression body ReSharper seems like to have no problems anymore as the red marked area goes away.

Is this a known problem, or are there other things known as cause?

Is there a known workaround (I already tried to clear the cache and dis/enable ReSharper)?

Would be shitty if this new C# 7.0 feature won't work with ReSharper.

Answer 1

According to this blog post, the latest version of ReSharper (2016.3) has "early support for C# 7" (emphasis mine). This means that not all C# 7 features are going to work right now (the post explicitly mentions some features that are supported, but does not mention expression-bodied getters and setters). Presumably this will be fixed in a later version, possibly the one released when the RTM version of VS 2017 is released.

Considering that C# 7 is still being developed, I don't think you should expect full support from tools like ReSharper.