Bug 2801 - The rename refactoring operation is broken
Summary: The rename refactoring operation is broken
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2012-01-09 11:00 UTC by Alan McGovern
Modified: 2015-08-20 03:24 UTC (History)
2 users (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 Alan McGovern 2012-01-09 11:00:04 UTC
In this code, right click on the definition of the Foo enum and choose to rename it to 'FooEnum'.  This causes the property declaration in 'Second' to be changed to:

FooEnumClass.Foo FooProperty {
     get; set;

which is clearly incorrect. See screencast link after this sample code:

namespace Foobar
	class MainClass
		public enum Foo
	public class Second
		MainClass.Foo FooProperty {
			get; set;	
		public Second ()
			FooProperty = MainClass.Foo.Value1;



New resolver branch, b00a2d77b6.
Comment 1 Mike Krüger 2012-01-16 05:48:23 UTC