Bug 1313 - Go To Definition command should prefer non-designer class parts
Summary: Go To Definition command should prefer non-designer class parts
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-06 12:04 UTC by Mikayla Hutchinson [MSFT]
Modified: 2011-10-07 08:30 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 Mikayla Hutchinson [MSFT] 2011-10-06 12:04:37 UTC
If a class has multiple parts, the Go to Definition command context menu shows a list of the parts. They should be sorted so that non-designer parts come before designer parts.

Also, if the Go to Definition command is run directly on a type that has multiple parts, it shows a pad with the parts. These should be sorted similarly.

I have some logic to sort the parts of a type based on whether they're designer
parts but I'm still trying to figure out where it should go in the MD API space.
Comment 1 Mikayla Hutchinson [MSFT] 2011-10-07 08:30:37 UTC
Fixed in master.