Bug 5759 - Images not selectable in dialog
Summary: Images not selectable in dialog
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.2.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2012-06-19 15:15 UTC by Dylan
Modified: 2013-11-20 07: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 Dylan 2012-06-19 15:15:23 UTC
I add a resource into the Drawables folder through Visual Studio. It's Build Action is set to AndroidResource. 

I have closed and opened the designer. I have built the project. But whatever I do, except for restarting Visual Studio, the image does not display in the dialog that pops up when pressing the button to select ImageView's src property.
Comment 1 Lluis Sanchez 2012-06-21 12:38:41 UTC
Which Mono for Android version are you using?
Comment 2 Dylan 2012-06-21 12:39:17 UTC
Comment 3 Lluis Sanchez 2013-03-13 07:52:16 UTC
Do you still have this problem with the latest version of Xamarin.Android?
Comment 4 PJ 2013-11-19 17:04:49 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 Dylan 2013-11-20 05:28:39 UTC
I haven't experienced this issue in a while and can be closed.
Comment 6 Lluis Sanchez 2013-11-20 07:30:52 UTC
Ok, closing.