Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 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.
I've just seen this tweet:
> Shaun McDonnell @McShauno
> You type something into the 'Immediate' window and 10 seconds later you *might* get a result when using MonoDroid.
The tweeter is clearly in a bad mood - so ignore the worst of his trolling - he'll come back after trying xcode and eclipse :)
However, he does have a valid point about the Immediate window in VS2010 and VS2012 - I use that window a lot in my non-Mono Dev, but in MonoDroid I don't touch it - as using it usually causes VS to hang in my experience.
If you try it during a debug session, then I think you'll see the problem straight away. If not - if you need more info about my setup and some repro steps - then please post here and I'll dump them out.
Vinicius, has this been addressed?
Can you make a simple screencast using Immediate Windows on VS? Thank you.
I don't have a working droid device to hand at present... can you test against a real device?
I have checked this issue with latest build. and its working fine at my end. Could you please recheck this issue on latest build and let we know if you getting same behavior on latest build.
This is still an issue with results from MongoDB's official C# driver. If you are debugging your code and you wish to see the result of a query, you find yourself putting a temporary variable into your code with a .toList() first and stepping through that, then the resulting variable can be viewed quickly in the immediate window. If you tried to do a .toList() directly in the immediate window, Xamarin has a good chance of timing out on the query or completely locking up.
It doesn't sound like an integration issue, and more like an external issue.
Marking as resolved downstream.
Please feel free to reopen the issue if you can still reproduce it with current bits.