I've had this happen to me a couple of times. Now I won't do an update
until there is a lull in project work and I think I can survive the time it
would take to get things working again. Which is annoying because each
update brings the hope that some of the annoying bugs will be fixed.
Including the bugs in the update process.
"If we can hit that bullseye, the rest of the dominoes
will fall like a house of cards... checkmate!"
-Zapp Brannigan, Futurama
On 19 September 2016 at 12:58, Greg Keogh <gfke...@gmail.com> wrote:
> Folks, on Friday Xamarin Studio told there were updates available, this
> happens every month or so, so I said "sure" and let it go.
> This morning I find compile errors relating to casts, arrays and
> IEnumerable that make no sense, like the compiler has become stupidly
> aggressive. Then I discover I can't open a XAML page because the Android
> SDK is outdated, and after tedious web searches reveal what to do it looks
> like the SDK Manager is downloading gigwatts of updates. Then the iOS 9
> iPad has vanished from the device picker and I only see iOS 10 Retina and
> Air devices listed. Worst of all, the app no longer runs in the iOS
> simulator and simply flashes and closes with no error, leaving me no way to
> diagnose what's wrong.
> So basically, this update has fried me to hell and I'm going to lose at
> least a full days work. Anyone else using Xamarin Studio beware.
> Things like this shouldn't happen in this day and age.