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.
Created attachment 3583 [details]
Two solutions and the error from trying to remove one.
I have created a new Android solution called AnimationTest. I selected the Android Application. When Xamarin.Studio created the project, it opened/added the solution XaminarAnimation to the list of open solutions. When I try to close one of the solutions, I get the error displayed in the following screenshot. The solution that I tried to close (XaminarAnimations) does not close and remains open in the IDE.
This happens each time I try to create an Android Application project/solution. The workaround is to restart Xamarin Studio.
What is the text of the exception? The screenshot does not show enough of it.
Can't duplicate this error, so can't tell you what the exception is. :(
You might be able to find it in your log files.
grep TargetInvocationException ~/Library/Logs/XamarinStudio-4.0/*Ide*
Grepping the log files returns nothing - if this occurs again I'll update this bug.
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.
Haven't been able to duplicated this in about 6 months. Marking this as RESOLVED / INVALID as some build since 2013/03/13 must have fixed the issue.