[Monodevelop-devel] Improving refactoring after 2.0

Mike Krüger mkrueger at novell.com
Fri Nov 7 02:41:47 EST 2008


> Notice that change previewing for the rename operation can be done with
> the current infrastructure. It's a matter of finding the references,
> displaying them and do the replace when the user clicks on OK. The API
> supports that, although we haven't implemented the GUI.

No not really. It's a hack. There is an operation called:

IMember RenameMember (RefactorerContext ctx, 
                      IType cls, 
                      IMember member, 
                      string newName);

And that's it. Ok you've:
MemberReferenceCollection FindMemberReferences (RefactorerContext ctx,
string fileName, IType cls, IMember member);

> > 
> > I'll need to extend/change the current refactoring infrastructure for
> > this. And one of the goals for the new one is: unit test support. The
> > new code completion infrastructure is tested with unit tests and I think
> > that this has improved the code completion correctness greatly.
> > 
> > Any thoughts/inputs here ?
> I'd like to see a high level design of the API to get an idea of how you
> plan to improve the refactoring infrastructure.
> Thanks!
> Lluis.

More information about the Monodevelop-devel-list mailing list