The big breaking change

We’re getting closer to the stable 4.0 release. Yesterday, we pushed out new NuGet packages with all the changes since beta7. There have been many. We have decided to make it more clear what each NuGet package does and have abandoned the HotTuna and Cirrious from the package names and from the namespaces. Everything that was named Touch (as in MonoTouch) is now named iOS (as in Xamarin.iOS). Also, we have decided to restructure the project while we were at it. This means going from beta7 to beta8 will be a bit involved, because of these namespace changes. To help you get started with the upgrade, please have a look at the upgrade documentation. See the package list for a full list of the new package names. We’re getting closer to the stable 4.0 release. Yesterday, we pushed out new NuGet packages with all the changes since beta7. There have been many. We have decided to make it more clear what each NuGet package does and have abandoned the HotTuna and Cirrious from the package names and from the namespaces. Everything that was named Touch (as in MonoTouch) is now named iOS (as in Xamarin.iOS). Also, we have decided to restructure the project while we were at it. This means going from beta7 to beta8 will be a bit involved, because of these namespace changes. To help you get started with the upgrade, please have a look at the upgrade documentation. See the package list for a full list of the new package names.

Xamarin.Mac

There have been changes on the Mac side, too. While versions since 3.5 supported MonoMac, Xamarin.Mac (Classic), Xamarin.Mac (Unified), beta8 and later versions will only support Xamarin.Mac (Unified). The good news: beta8 is the first version to have working Nugets for Mac. If you’re new to MvvmCross on Mac, simply create a PCL and a Xamarin.Mac (Unified) project in your solution and add the MvvmCross.StarterPack Nuget to those projects to have sample code created to help you get started. There have been changes on the Mac side, too. While versions since 3.5 supported MonoMac, Xamarin.Mac (Classic), Xamarin.Mac (Unified), beta8 and later versions will only support Xamarin.Mac (Unified). The good news: beta8 is the first version to have working Nugets for Mac. If you’re new to MvvmCross on Mac, simply create a PCL and a Xamarin.Mac (Unified) project in your solution and add the MvvmCross.StarterPack Nuget to those projects to have sample code created to help you get started.

Other changes

For a full list of changes see the merged PR’s of the repositories.

• MvvmCross
• Android-Support
• Forms
• Plugins
• Samples

The new release is available on Nuget.

See the issue list for an overview of all solved issue’s and merged pull requests. Those lists are also available for Android Support and MvvmCross Forms

If you need any help you can get in touch via Slack, or open a topic on StackOverflow and tag it with “MvvmCross”.

Let us know if you find any bugs!

• Martijn00
• Cheesebaron ʕ•̫͡•ʔ
• Kerry