2016.1 reintroduces wrong MVVM WPF suggestions

After upgrading to 2016.1 ReSharper is back to suggesting public View Model properties which must be public in order to be used from the view which does not specify this VM to be it's Data Context in XAML should be made private with 'Member can be made private' suggestion, even though it finds dynamic usages of that property in XAML of view(s) using the property.

This was resolved with one of previous versions and now we're back to old invalid behavior... why is this and is there a way to prevent this without using the "Do not show" option for this inspection?

2 comments
Comment actions Permalink

Hello Dean,

Have you used Agent Mulder plugin in previous R# installation (10.0.2)? Since such plugin provides the behavior you are expecting to see. But right now the plugin is not compatible with the latest R# version https://github.com/hmemcpy/AgentMulder. 

Thanks! 

0
Comment actions Permalink

Hi Alexander, I did not have any extensions installed in 10.0.2...

0

Please sign in to leave a comment.