在VS2015更新2中使用npm安装角2包的问题

时间:2022-04-09 13:46:54

I am attempting to use the latest angular2 quickstart files with a new empty ASP.NET Core 1.0 Web Application.

我正在尝试使用最新的angular2 quickstart文件和一个新的空ASP。NET核心1.0 Web应用程序。

VS2015 Update 2 - w/ Core 1.0 RC2 installed

VS2015更新2 - w/ Core 1.0 RC2安装

Steps to reproduce:
Create a new project using ASP.NET Core Web Application (.NET Core) - Empty Template

复制步骤:使用ASP创建一个新项目。NET Core Web应用程序(。NET Core) -空模板

Add the 4 angular quick-start files to your root directory, NOT Hitting save on package.json until the other 3 are added and saved.

将4个角快速启动文件添加到根目录中,而不是在包上单击save。json直到添加和保存其他3个。

Finally, hit save on package.json and npm will start installing all of the packages. However, at the end I see Dependencies - not installed, npm - not installed. I can't figure out what could be causing this. It has to be a VS2015 / npm bug because if I use VSCode and npm from command line everything installs perfectly with this package.json file.

最后,点击save on package。json和npm将开始安装所有包。然而,在最后,我看到依赖项——没有安装,npm——没有安装。我不知道是什么引起的。它必须是一个VS2015 / npm错误,因为如果我使用命令行中的VSCode和npm,那么所有东西都将与这个包完美地安装在一起。json文件。

1 个解决方案

#1


3  

This is a bug in the Web Tools for ASP.NET Core RC2, which was discovered after RC2 was shipped. It's only that the "- not installed" UI is showing up incorrectly. The packages are successfully installed.

这是ASP的Web工具中的一个缺陷。NET Core RC2,在RC2发布后被发现。只是“未安装”UI显示不正确。软件包已经成功安装。

I'm not sure what is causing it yet, but we are aware of the issue and will try to fix this in a future release of the Web Tools.

我不确定是什么原因导致了这个问题,但是我们已经意识到了这个问题,并将在未来的Web工具版本中尝试解决这个问题。

#1


3  

This is a bug in the Web Tools for ASP.NET Core RC2, which was discovered after RC2 was shipped. It's only that the "- not installed" UI is showing up incorrectly. The packages are successfully installed.

这是ASP的Web工具中的一个缺陷。NET Core RC2,在RC2发布后被发现。只是“未安装”UI显示不正确。软件包已经成功安装。

I'm not sure what is causing it yet, but we are aware of the issue and will try to fix this in a future release of the Web Tools.

我不确定是什么原因导致了这个问题,但是我们已经意识到了这个问题,并将在未来的Web工具版本中尝试解决这个问题。