Why would VS 2017 suggest replacing a property with a method?

Viewed 1329

I noticed that every property in Visual Studio 2017 has a quick action that suggests replacing it with a method.

enter image description here

Is that mean that properties is not the recommended way to set and get fields value, do Microsoft intend to deprecate it in the future?!

Or are there any gains that could be achieved using methods over properties for that purpose?

1 Answers
Related