none
Valid Nuget Packages Fail to Install on Visual Studio 2015

    Question

  • I'd like to request guidance on which of Xamarin, Visual Studio, PowerShell, or Nuget, to file a bug-report about the following, as well as how to resolve it in the meantime.

    The circumstance is that installing a Nuget Package is rejected by Visual Studio 2015, and yet it installs properly on Visual Studio 2013.

    The salient error detail is as follows, which considering it installs in Visual Studio 2013, and yet not on Visual Studio 2015, would seem to be erroneous:

    Install-Package : Could not install package 'Microsoft.AspNet.WebApi.Client 5.2.3'. You are trying to install this package into a project that targets 'MonoAndroid,Version=v6.0', 
    but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
    At line:1 char:1
    + Install-Package Donky.Core
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
        + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand

    I belong to the company which is the Package Author, and as a test I built a separate Nuget Package that instead of installing version 5.2.3 of Microsoft.AspNet.WebApi.Client, required that version 5.1.0 was installed instead: this installed on Visual Studio 2015!

    i.e. I changed the following line in the nuspec file:
    <dependency id="Microsoft.AspNet.WebApi.Client" version="5.2.3" />
    to
    <dependency id="Microsoft.AspNet.WebApi.Client" version="[5.1.0,5.1.1)" />

    We don't, however, want to publicly reissue the Nuget Package with a version 5.1.0 dependency instead of a version 5.2.3 dependency, as the problem is not a Nuget package problem, but a tooling problem.

    The question is, which tool is causing the problem, and hence who should we file the bug report to?

    The bug itself is easily reproducible, just create a new Xamarin Forms PCL solution on both of Visual Studio 2013 and 2015 and run the following command in the Package Manager console, against the Android project:

    PM> Install-Package Donky.Core

    The Visual Studio 2013 one should successfully install, and the Visual Studio 2015 will not successfully install.

    We ran this test on two different MacBook workstations with Visual Studio 2013 and 2015 installed in different VM mechanisms, both in Windows 10, but with the same result.

    Every assistance will be appreciated!

    Kind regards.

    Tuesday, November 10, 2015 11:48 AM

Answers

  • Hi Xamtastic,

    Thank you for posting in MSDN forum.

    I tested this issue on my visual studio 2015, the same issue as yours:

    So I suggest you could submit this issue on Microsoft Connect feedback portal: https://connect.microsoft.com/VisualStudio/feedback/CreateFeedback.aspx , Microsoft engineers will evaluate them seriously.  After you submit the feedback, you can post the link here which will be beneficial for other members with the similar issue.

    Thank you for your understanding.

    Best Regards,

    Jiayi


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Wednesday, November 11, 2015 5:29 AM
    Moderator
  • Hi Jiayi,

    Thanks for confirming the issue!

    I've lodged the bug report with Nuget here:

    https://github.com/NuGet/Home/issues/1707

    And it's been added to Nuget's Milestone 3.4 targets here:

    https://github.com/NuGet/Home/milestones/3.4

    Thanks for your feedback, presuming that the issue is resolved in Nuget's 3.4 release, I should think that we can consider the issue now closed, other than needing to manage user expectation until it is resolved.

    Kind regards!


    - Xamtastic "Oh Shakespeare, shall I compare Xamarin to a summer's day?" www.xamtastic.com

    • Marked as answer by Xamtastic Thursday, November 19, 2015 6:40 AM
    Thursday, November 19, 2015 6:39 AM

All replies

  • Hi Xamtastic,

    Thank you for posting in MSDN forum.

    I tested this issue on my visual studio 2015, the same issue as yours:

    So I suggest you could submit this issue on Microsoft Connect feedback portal: https://connect.microsoft.com/VisualStudio/feedback/CreateFeedback.aspx , Microsoft engineers will evaluate them seriously.  After you submit the feedback, you can post the link here which will be beneficial for other members with the similar issue.

    Thank you for your understanding.

    Best Regards,

    Jiayi


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Wednesday, November 11, 2015 5:29 AM
    Moderator
  • Hi Jiayi,

    Thanks for confirming the issue!

    I've lodged the bug report with Nuget here:

    https://github.com/NuGet/Home/issues/1707

    And it's been added to Nuget's Milestone 3.4 targets here:

    https://github.com/NuGet/Home/milestones/3.4

    Thanks for your feedback, presuming that the issue is resolved in Nuget's 3.4 release, I should think that we can consider the issue now closed, other than needing to manage user expectation until it is resolved.

    Kind regards!


    - Xamtastic "Oh Shakespeare, shall I compare Xamarin to a summer's day?" www.xamtastic.com

    • Marked as answer by Xamtastic Thursday, November 19, 2015 6:40 AM
    Thursday, November 19, 2015 6:39 AM