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 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.
See video: http://screencast.com/t/hdYbpqCRSjXo
Project to repo: http://dl.dropbox.com/u/90453/PhotoPicker.zip
Line 109 in OverlayViewController.cs
Hope this helps,
Y, it's a bug in mcs - reported upstream.
*** Bug 492 has been marked as a duplicate of this bug. ***
Is this likely to get fixed for 2.8? If not, should we hold up the release for it?
works in new resolver branch.
This is still an issue in the 2.8.5 release and needs to be fixed for 2.8.*. Here's another video of the issue: http://screencast.com/t/KjLcM5ftZ
Replacing the mcs in 2.8.* would have unexpected side effects - the mcs ast generation changed too much.
What's the bug # in mcs? I'm uncomfortable resolving a highest priority bug with no idea when or how the bug is actually going to be addressed for users?
The bug is that mcs doesn't parse that. The bug is addressed, but the fix is not ready yet.
Mcs parsing changed too much & I'm not going to introduce destabilizing side effects in the 2.8.x line again. The last backport caused more harm than good.
TBH that is not anywhere near a "highest priority" bug. This doesn't cause crashes or data loss in any way.
I know that everyone wants their favorite bug fixed asap, but in the 2.8.x line only crashes/data loss bugs will get fixed on that layer. Replacing mcs would require investing some days in a backport which will cause side effects & maybe update even nrefactory ...
Setting that to "high".
Fixed in 2.9.1/newresolver.