0

I am trying to install Humanizer (see also GitHub and NuGet Gallery pages) using the NuGet package manager inside Visual Studio 2010. The documentation suggests it should support .NET 4+.

Issuing the following command on a brand new empty MVC4 project:

PM> install-package Humanizer

Gives me the following result:

Successfully installed 'Humanizer 1.26.1'.
Successfully uninstalled 'Humanizer 1.26.1'.
Install failed. Rolling back...
Install-Package : Could not install package 'Humanizer 1.26.1'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.0', but the package does not contain any assembly references that are compatible with that framework. For more information, contact the package author.
At line:1 char:16
+ install-package <<<< Humanizer
+ CategoryInfo : NotSpecified: (:) [Install-Package], InvalidOperationException
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand

PM>

I contacted the author directly (and subsequently raised an issue on GitHub). He mentioned that the package targets Profile136 (can also be seen in the csproj file) which should support .NET 4:

<TargetFrameworkProfile>Profile136</TargetFrameworkProfile>

I had a look around and read this SO question which discusses building portable class libraries. Having read that, I discovered that Visual Studio 2010 requires an add-in to enable building of PCLs.

I realise I'm not building here, but I installed it anyway, along with the updated reference assemblies v4.6.

Having looked in the following folder:

C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETPortable\v4.0\Profile

I discovered that I only have profiles up to 131, but no 136.

An answer to the SO question mentioned earlier suggests that 136 was added in the Windows Phone SDK 8.0. However I can't install this on Windows 7.

Why can't I install this package in Visual Studio 2010? Is it because I don't have profile 136 on my machine, or is that only required for building PCLs?

Note that I have installed other NuGet packages successfully, e.g. log4net.

Community
  • 1
  • 1
Sir Crispalot
  • 4,792
  • 1
  • 39
  • 64
  • 1
    Strange. You should not need to have the Portable Class Libraries installed to install the Humanizer NuGet package into a project that targets .NET 4.0. The Profile 136 is in the Portable v4.6 reference assemblies - to install it you need to unzip the zip file that the installer installs. However you should not need to have any PCLs installed. To test this I renamed the .NETPortable library and with an empty MVC 4 project could add a reference to Humanizer in VS 2010. Do you have a recent version of NuGet installed? – Matt Ward Jun 17 '14 at 18:55
  • Also might be worth looking at the Humanizer NuGet package in the cache on your local machine (C:\Users\UserName\AppData\Local\NuGet\Cache) and see what it contains. – Matt Ward Jun 18 '14 at 08:34

1 Answers1

2

You should not need to have the Portable Class Libraries installed to add the Humanizer NuGet package to a project that targets .NET 4.0.

The Profile 136 is in the Portable v4.6 reference assemblies. To install this you need to unzip the zip file that the installer installs. However you should not need to have any PCLs installed.

As a test I renamed the .NETPortable library directory so NuGet did not detect the portable libraries. Then with an empty ASP.NET MVC 4 project I could add a reference to Humanizer in Visual Studio 2010.

If you have a recent version of NuGet installed then it should work.

Matt Ward
  • 47,057
  • 5
  • 93
  • 94
  • 1
    Thank you so much @MattWard. I upgraded NuGet from 2.0.30717.9005 to 2.8.50313.31 and the package installed correctly. – Sir Crispalot Jun 18 '14 at 09:31