Bug 13833 - [NRefactory] Refactoring a method name changes other methods with the same name
Summary: [NRefactory] Refactoring a method name changes other methods with the same name
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.1.8
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-08-07 17:09 UTC by Stephen Shaw
Modified: 2013-08-13 02:38 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Stephen Shaw 2013-08-07 17:09:03 UTC
I'm porting some java code over to c# and ran into this.

Notice that both methods have set changed to Set.

Before name refactor
public void setFocusedWindow(Activity activity) {

public void setFocusedWindow(View view) {

After name refactor
public void SetFocusedWindow(Activity activity) {

public void SetFocusedWindow(View view) {
Comment 1 Mike Krüger 2013-08-08 01:06:00 UTC
Atm this is a feature - ppl always wanted to rename the MethodGroup not individual overloads.
Comment 2 Mike Krüger 2013-08-13 02:38:54 UTC
The rename dialog has now a check box where the user can choose to rename the overloads or not.

I don't see another way that works with all use cases - but I think it's ok doing it that way.