I updated MVVMCross 5.1.1 to 5.2.0 in a sample project (TipCalc) with Android and UWP. Nuget offered this update an I just updated using VS2017 nuget view.
After this two things happend:The UPW designer tells me that views:MvxWindowsPage doesn't exist in the namespace MvvmCross.Uwp.Views. So I have no longer a working designer.
Rebuild brings up these warnings
...TipCalc.UI.Droid.csproj : warning XA0105: The $(TargetFrameworkVersion) for MvvmCross.Binding.Droid.dll(v7.0) is greater than the $(TargetFrameworkVersion) for your project(v6.0). You need to increase the $(TargetFrameworkVersion) for your project.
...TipCalc.UI.Droid.csproj : warning XA0105: The $(TargetFrameworkVersion) for MvvmCross.Droid.dll (v7.0) is greater than the $(TargetFrameworkVersion) for your project(v6.0). You need to increase the $(TargetFrameworkVersion) for your project.
...TipCalc.UI.Droid.csproj : warning XA0105: The $(TargetFrameworkVersion) for MvvmCross.Platform.Droid.dll (v7.0) is greater than the $(TargetFrameworkVersion) for your project(v6.0). You need to increase the $(TargetFrameworkVersion) for your project.
Starting it on the emulator crashes the app. The droid project is set to Marshmellow (6.0).
Does the MVVMCross 5.2 version need Lollipop (7.0) - or did I something wrong when updating?
You'll need to install the Android 7.0 SDK using the SDK manager. You app should also be set to compile against the latest version, so it should pick this up automatically.
MvvmCross uses the latest Android support libraries, and these use the 7.0 SDK.