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.
Description of Problem:
I installed Xamarin 2.0
This bug is only reproduced in Visual Studio 2010. It's good for Visual Studio 2012.
Steps to reproduce the problem:
1. After installation Xamarin Visual Studio Integration,
2. Create a new Visual Studio Solution, and create 2 projects (ConsoleApp, Library)
3. Unload Library project using Visual Studio Solution Explorer's context menu
4. Close solution, and reload it.
You can miss it, the unloaded project is still loaded.
The unloaded project has to be unloaded.
How often does this happen?
After uninstallation of Xamarin.iOS, Xamarin.Android, unloaded project is unloaded.
In Visual Studio 2012, it's OK. Only in Visual Studio 2010.
Today, We have checked this issue with following builds:
Now , its working fine, the unloaded library project from solution explorer in VS is not loaded When we reopen the Console application in VS. Hence marking this as Verified Fixed.
This is happening again with 1.8.365 on VS 2013
@Dominique I have checked this issue with: MTVS 1.8.365 and 1.10.39.
We are getting same behavior with both MTVS
Steps that I have followed:
1. Create a console app in VS.
2. Add iOS Library project in solution
3. Unload the library project
4. Close the solution
5. Observe that after clicking on close solution, we are getting Save file changes with 'Yes' and 'No' option.
We have checked with the options and observation as follows:
Case 1: If we click on 'Yes' Button and reopens the VS with Same project, then unloaded Library project appears as loaded in Solution Explorer of VS.
Screencast for the same: http://screencast.com/t/1aGq1IpI5Amo
Case 2: If we click on 'No' button and reopens the VS with same project, then unloaded Library project doesn't appears in Solution Explorer of VS.
Screencast for the same: http://screencast.com/t/pny8KMR5dlu
Please review let us know, if we have to check anything additional.
Love the fact that's still on the last stable and no commentary after a month and half. Guess it's a feature now ?
Anybody there ?
This is still present in 1.12...
Are you putting me on ?
Re-checked with new versions:
- Window 7 64-bit
- VS 2010, VS 2012
- Xamarin for Windows 1.12.278, 2.00.100, and development build that fixes bug #17334.
I was able to reproduce the bug in:
VS 2010, VS 2012
1.12.278 and 2.00.100
But, some good news is that the bug is _fixed_ for both VS 2010 and VS 2012 in the development build for bug #17334.
With just a little luck the fix should be in the next beta release after the current beta version (2.00.100) moves to stable.
## Additional partial workaround
Just in case it might be helpful until the bug fix is released, I noticed along the way that logging out of my Xamarin account ("Tools -> Xamarin Account") was sufficient to stop the problem.
It's not a complete workaround since it doesn't help when working on Xamarin projects in solutions that also contain unloaded projects, but it might be helpful for solutions that don't contain any Xamarin projects.
Thanks for the report!
Hey who in the world are you ? :)
You're the first person in this bug tracker which actually did what one would expect (although months and iterations late). Besides Dominique actually
Hope this is not an isolated incident (and that someone replies to my bug tracker more reliably)
For other users who might run across this bug and wonder about absent replies on bug reports, be sure to bother us by e-mail at firstname.lastname@example.org.
We on the support team can double-check the issues, run additional tests if needed, update/reopen bugs, and make sure new information gets seen in the right places!
Good to hear, albeit a tad late...I probably ate my liver in the last year trying to get some attention here