Effectively propagate interface changes in Visual Studio

Question

As I delve into the world of dependency decoupling and injection, I find that I am writing more and more interfaces. I try to create interfaces, knowing exactly how I will use them, but it always happens that I end up implementing an interface and then changing its use.

I'm used to the ability to automatically refactor VS. But I found that it does not support the automatic propagation of interface changes to implementation classes. Is there a way to do this automatically so that I don't copy and paste until my compilation errors go away?

Answer 1

I wanted to come back and answer this question:

If you want to change the name of an interface method, if you change it from an instance class, Visual Studio will give you the opportunity to extend it to the interface (like all other calls on your code, as usual). If you change the method name in the interface definition, this change will not apply to instance classes.

Answer 2

Since Visual Studio or any other tool cannot "know" what the implementation is, you have to, the developer, to implement it.

If you change the interface definition, it’s good that the compilation failed until you make this change.