我试图重新创建您的问题，并与类似的错误想出了当溶液在Visual Studio 2013创建，然后试图建立它在VS 2015我能得到一个成功的构建一旦我重新安装的NuGet包管理器（和闭环>重新VS 2015）。

I attempted to re-create your issue and came up with a similar error when the solution was created in visual studio 2013 and then tried building it in in vs 2015. I was able to get a successful build once i reinstalled NuGet Package Manager (and closed->reopened VS 2015).

参考/信用。有关于通过与2015年VS早期版本的NPM（即我只是沿着我所尝试和摸索出合格）建设若干问题的SO问题。经常性的分辨率通常是更新/重新安装电源外壳NPM或更改执行策略。我倾向于喜欢更新+重启的办法，以避免与Windows中的黑盒子修修补补。一个来源： http://***.com/a/32251092/1158842 也可能有MSBuild的集成解决方案的问题在这种情况下，溶液中的迁移距离的NuGet资源远可以做的伎俩。来自： http://***.com/a/31811461/1158842

References / Credit. There are several SO questions relating to build issues via with earlier version of NPM for VS 2015 (ie i'm just passing along what i've tried and worked out). Recurring resolution is usually update / reinstall NPM or change execution policy in power shell. I tend to like the update + restart approach to avoid tinkering with the black boxes in windows. one source: http://***.com/a/32251092/1158842 There may also be an issue of MSBuild Integrated solutions, in which case migrating away from the nuget resources in the solution could do the trick. from: http://***.com/a/31811461/1158842