Stable Release: Xamarin.Mac 2.0.2.111, Cycle 5 – Service Release 3

BrendanZagaeskiBrendanZagaeski USForum Administrator, Xamarin Team Xamurai
edited August 2015 in Xamarin.Mac
  • xamarin.mac-2.0.2.111.pkg (6db87c5)
  • MonoFramework-MDK-4.0.3.20.macos10.xamarin.x86.pkg (d6946b4)

Reason for release: Additional bug fixes for the "Cycle 5" Stable Release on April 29 and the previous Cycle 5 Service Releases. (See the release blog for a short description of "Cycles" and "Service Releases.")

Date published: See https://releases.xamarin.com/.

These versions are unchanged from the Cycle 5 – Service Release 3 Beta release.

Previous versions, downgrading

You can downgrade back to the previous Stable version by manually reinstalling each old package. See the KB article on downgrading. If you have a Trial or Starter subscription, feel free to contact hello@xamarin.com to request the older versions.

Older Mono package versions are not currently listed on https://store.xamarin.com/account/my/subscription/downloads. The Mono package for the previous Stable version ("Service Release 2") is available here:

Older versions (from before April 29)

If needed, you can downgrade back to older versions (from before April 29) by manually reinstalling each old package. See the "Previous versions, downgrading" section on the April 29 Stable release thread for the older downgrade links.

Guidelines for this thread

  1. This first post will be updated regularly.

  2. Hopefully this thread will help answer "what might break if I update to this release?"

  3. If you find a new problem that is specific to this version, please file a bug report.

  4. Please discuss older bugs that are unchanged in this release compared to the previous Stable version in Bugzilla instead.

  5. Of course for questions and discussions about topics other than bugs, feel free start new forum threads.


EDIT Aug 21: Correct the section on downgrading.

Posts

  • pmhart83pmhart83 USMember ✭✭✭

    @BrendanZagaeski

    We are currently still on 2.0.1.64 because any newer version would randomly crash because events where being fired with UI objects as event argument parameters.

    Any idea if this has been fixed in 2.0.2.111?

Sign In or Register to comment.