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.
If you try, you will get http://screencast.com/t/v0ZREDqH6Mz (The operation could not be completed. Invalid Pointer)
Steps to reproduce:
Create an MFA project
Create a second MFA project
Double click the .axml file in Resources/Layout
Designer should open
Workaround: Restart VS
Setting severity to major because it looks pretty bad. Not setting it higher because there is a workaround and many users will just be editing one solution.
Here's the build log to RC4:
checkout firstname.lastname@example.org:xamarin/AndroidVS to c:\cygwin\tmp\source/AndroidVS at 8d8783e19e14587bb9e9f959b30942ce5921180d
So RC4 contains the 9a6a8f7c commit.
This was found on RC4 of MFA 4.2 (sorry for not including).
Running mandroid.exe --version and sending the output to a text file I get: monodroid 220.127.116.11383603
That's the right output so something is still occurring that shouldn't be.
My bad, I misunderstood what this bug was about.
Fixed in aa4d4b76ef6b29cc742488536e96868eb90f3a83.
Verified fixed in MFA 4.2.0 RC5
Created attachment 3514 [details]
Log from Case #27070