Bug 30270 - [Roslyn Migration] XS places event handler method inside another method
Summary: [Roslyn Migration] XS places event handler method inside another method
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2015-05-20 13:14 UTC by Oleg Demchenko
Modified: 2015-11-17 04:16 UTC (History)
3 users (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:
VERIFIED FIXED

Description Oleg Demchenko 2015-05-20 13:14:41 UTC
Still experiencing problems with wiring events. Steps to reproduce:
1.  Create new iOS proj in XS
2.  Open ViewController.cs
3.  Try to create event handler using autocompletion

Actual behaviour: 
1) refactoring tool places event handler method inside another
method(ViewDidLoad in my case)
2) it leads to situation when user can't escape method's scope using up and
down buttons

Screencast: http://screencast.com/t/SvKLpUQEMUu6
Tested with XS Version 6.0 (build 2249)
Comment 1 Udham Singh 2015-05-21 10:29:17 UTC
I have checked this issue and able to reproduce the reported behaviour. Please refer the screencast : http://www.screencast.com/t/2ELzKRpLo7N

Ide Log : https://gist.github.com/Udham1/818e24846e06adf2a07f

Environment Info : 

=== Xamarin Studio ===

Version 6.0 (build 2248)
Installation UUID: ce927b2a-2c07-44c5-b186-09cfdafba6dc
Runtime:
	Mono 4.0.1 ((detached/11b5830)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400010043

=== Apple Developer Tools ===

Xcode 6.2 (6776)
Build 6C131e

=== Xamarin.iOS ===

Version: 8.10.1.61 (Enterprise Edition)
Hash: bd0e341
Branch: master
Build date: 2015-05-20 21:56:40-0400

=== Xamarin.Android ===

Version: 5.1.2.1 (Enterprise Edition)
Android SDK: /Users/xamarin76/Desktop/android-sdk-macosx
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: 2.0.1.61 (Enterprise Edition)

=== Build Information ===

Release ID: 600002248
Git revision: 67be24fd214dd94da0257345afbe40d3d080a6e4
Build date: 2015-05-20 09:30:09-04
Xamarin addins: 62ed056ec0b8734284c18c4e39ec4c6d3a89b520
Build lane: monodevelop-mdaddins-adcodebehind

=== Operating System ===

Mac OS X 10.9.5
Darwin Xamarin76s-Mac-mini.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 2 xamarin-release-manager 2015-05-29 10:20:29 UTC
Fixed in version 6.0.0.2407 (roslyn)
Comment 3 Shruti 2015-11-17 04:16:41 UTC
This issue is wokring fine with Roslyn XS 6.0 (build 1887).

Screencast: http://www.screencast.com/t/SMrNze6F9Cf
Environment Info: https://gist.github.com/Shruti360/b978dc9f4dbd7ac86800

Hence, Closing this issue.