Bug 5829 - Extract method insertion location is wrong
Summary: Extract method insertion location is wrong
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-06-22 14:33 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-07-18 03:15 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED NORESPONSE

Description Mikayla Hutchinson [MSFT] 2012-06-22 14:33:49 UTC
In the following case, the extract method insertion location is wrong:
http://screencast.com/t/a1TyiV7W1J

The first location is fine, but pressing Down moves the caret to the top of the document instead of below the existing method.
Comment 1 Mike Krüger 2012-06-22 17:04:59 UTC
It's not extract method - it's the insertion point calculation that fails in this file.
Comment 2 Mike Krüger 2012-07-16 04:10:22 UTC
Can't repro with master. I need the file if, you've it.
Comment 3 Mike Krüger 2012-07-18 03:15:17 UTC
Can't repo it (In the 3.0.x versions it surely had errors - as alan worked on the unit tests I've seen that the insertion point tests were failing) - if you've a use case reopen it.