Bug 6226 - #region and #endregion are swapped when implementing an interface
Summary: #region and #endregion are swapped when implementing an interface
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-07-21 12:47 UTC by Marcel Hellwig
Modified: 2012-11-30 03:08 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 Marcel Hellwig 2012-07-21 12:47:56 UTC
When you have a class with extending an interface and click right on the interface on the extending interface -> refactoring -> implement interface (explicit) something like this shows up


public void flush()
	throw new NotImplementedException();

public void save(System.Collections.Generic.KeyValuePair<string, object> pair)
	throw new NotImplementedException();

#region IPropertyFileOperations implementation

As you see, they are switched.
Comment 1 Marcel Hellwig 2012-07-21 13:14:18 UTC
I found out something interesting.
When I try to implement an abstract class, there are two options for refactoring, one direct below rename, and the other one, one position down, but seperated with a seperator. The first one (which is localized into my language (german)) works fine, but the other one, which is still in english, shows the same behavoir as I introduced with this bugreport.
Comment 2 Mike Krüger 2012-11-30 03:08:00 UTC
Should be fixed in newer builds.