Yes, this is a weakness of, essentially, slapping dynamic binding on top
of static binding. In practice, it's usually manageable because:
- each refactoring should be small
- things tend to be very local when developing with MO
- the good IDEs (Idea and Eclipse) will also do string replacement
during a rename
- if you get it wrong the tests will break so it's easy to find the
references
S.
Barry Kaplan wrote:
> What has been the experience (if any) of the use of refactoring tools
> when using the dynamic.Mock class? Specifically, the use of strings for
> specifying method names? With idea, I can ask to check for strings when
> performing a refactoring, but finding usages is out.
>
> I can't think of any other alternative though, so I though I would ask
> around.
|
