MvvmCross PortableSupport 3.1.1Library Installations Fails in Visual Studio 2013

MirMajeed.9898MirMajeed.9898 USMember, Developer Group Leader

I am trying to add the MvvmCross nuget package in PCL project in Visual Studio 2013 with Update 2 project and get the following error:

Install failed. Rolling back...
Could not install package 'MvvmCross.PortableSupport 3.1.1'. You are trying to install this package into a project that targets 'portable-net45+win+wpa81+MonoAndroid10+MonoTouch10', but the package does not contain any assembly references or content files that are compatible with that framework.

Posts

  • JonDouglasJonDouglas USXamarin Team, University, Developer Group Leader Xamurai

    Hey @MirMajeed‌ it's probably best to post an issue on the MvvmCross github page.

    https://github.com/MvvmCross/MvvmCross

  • mattwardmattward GBMember Xamurai

    NuGet does not believe the NuGet package is compatible with your project.

    Looking at the MvvmCross.Portable 3.1.1 NuGet package it has a folder, but no actual PCL assemblies. The folder indicates that it is targets:

    portable-win+net45+sl50+wp8+MonoAndroid+MonoTouch
    

    Your project is targeting:

    portable-net45+win+wpa81+MonoAndroid10+MonoTouch10
    

    NuGet will check every target framework that your project has against those in the NuGet package. In order for the NuGet package to be compatible it must have every target framework that your project has and each target framework version must have a version equal to or less than what is in your project.

    So looking at your project it seems to be that the wpa81 (WinRT-based Windows Phone Application) target framework is missing from the NuGet package so NuGet believes the package to be incompatible. Whilst the MvvmCross Portable NuGet package does target wp8 (Windows Phone 8) NuGet treats wpa81 (WinRT-based Windows Phone Application) as a different framework.

    It looks like the MvvmCross.Portable NuGet package will need to be updated so it also supports Windows Phone Application projects. As @JonDouglas already suggested, I would create an issue on the MvvmCross GitHub site. The other option is to change your project so it targets a different profile that is compatible.

Sign In or Register to comment.