[Monodevelop-devel] Improving refactoring after 2.0

"Andrés G. Aragoneses" aaragoneses at novell.com
Wed Nov 5 10:12:41 EST 2008

Mike Krüger wrote:
> Hi
> After the next release I want to improve refactoring. 
> Currently we only have rename as refactoring operation. Generally I want
> to do refactoring a bit different than it is now.
> I want a refactoring infrastructure that allows the user to preview all
> changes that are done in the refactoring step (see eclipse for an
> example). 
> 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 ? 

When you say next release, are talking about a 2.0 Alpha or 2.0 final?
If you mean final, perfect. If not, IMHO I would dedicate more time to
fix more basic use cases for refactoring features. I don't know if there
are still bugs open on bugzilla, but with a brief look I see many
regressions: go to declaration not shown in many cases, looking for
references takes a lot of time, etc..
I will see if I can report some of those, although it's difficult to
isolate them.



More information about the Monodevelop-devel-list mailing list