Bug 16153 - Updating from VS breaks VS Xamarin plugin
Summary: Updating from VS breaks VS Xamarin plugin
Status: RESOLVED DUPLICATE of bug 13349
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Updater ()
Version: 1.8.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-11-12 15:57 UTC by Seth Rosetter
Modified: 2013-11-12 16:09 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

screen1.png (26.79 KB, image/png)
2013-11-12 15:57 UTC, Seth Rosetter
screen2.png (26.79 KB, image/png)
2013-11-12 15:58 UTC, Seth Rosetter

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Seth Rosetter 2013-11-12 15:57:35 UTC
Created attachment 5407 [details]


Using Visual Studio 2012, I was prompted to update to the newest version of Xamarin.Android and Xamarin.iOS. I updated Android first. Then I tried to open an iOS project and the .csproj cased an error (screen1.png). Then I navigated to Tools -> Options -> Xamarin and saw that the iOS component could not load (screen2.png)
Comment 1 Seth Rosetter 2013-11-12 15:58:18 UTC
Created attachment 5408 [details]
Comment 2 PJ 2013-11-12 16:09:17 UTC

*** This bug has been marked as a duplicate of bug 13349 ***