当我在 Visual Studio 2013 中创建解决方案然后尝试在 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.

重新安装 NuGet 包管理器(并关闭，然后重新打开 VS 2015)后，我能够成功构建.

I was able to get a successful build once I reinstalled NuGet Package Manager (and closed, then reopened VS 2015).

参考文献/信用

有几个与通过早期版本的 NPM for VS 2015 构建问题相关的 SO 问题(即我只是传递我已经尝试和解决的问题).重复解决方案通常是更新/重新安装 NPM 或更改 Power Shell 中的执行策略.我倾向于喜欢更新 + 重新启动的方法，以避免修补 Windows 中的黑框.一个来源:https://***.com/a/32251092/1158842也可能是MSBuild集成解决方案的问题，在这种情况下，从解决方案中的 NuGet 资源迁移出去就可以了.

There are several SO questions relating to build issues via with earlier version of NPM for VS 2015 (i.e. 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: https://***.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.

来源:https://***.com/a/31811461/1158842