Bug 15340 - Code completion should prefer classes in same namespace
Summary: Code completion should prefer classes in same namespace
Status: RESOLVED DUPLICATE of bug 13103
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.12
Hardware: Macintosh Mac OS
: --- trivial
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-10-10 17:55 UTC by Tom Opgenorth
Modified: 2013-10-10 18:32 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 Tom Opgenorth 2013-10-10 17:55:49 UTC
When using the code completion in Xamarin Studio and Xamarin.Android should default to classes closest to the "home" namespace where possible. For example, the Resource class which is in the Android namespace as well as the namespace for a Xamarin.Android project. The Xamarin Studio code completion should prefer the Resource class from a Xamarin.Android project over the one that is from the Android namespace when typing in code.

See this screencast for how code completion defaults to Android.Resources instead of CalabashExamples.Droid.Resources:

To contrast, here is a screen cast of how this works in Resharper (i.e. expected behaviour):
Comment 1 Mikayla Hutchinson [MSFT] 2013-10-10 18:32:04 UTC

*** This bug has been marked as a duplicate of bug 13103 ***