I've added two well known projects to an ASP MVC application and it looks like the packages don't install under /Scripts and /Content as expected (CSS and JS are bundled together).
我在ASP MVC应用程序中添加了两个众所周知的项目，看起来这些包并不像预期的那样安装在/脚本和/内容中(CSS和JS是捆绑在一起的)。
Am I missing something? Do package authors assume that people will move content to the correct folders, or does no one use the default ASP MVC template folders?
我遗漏了什么东西?包作者是否假设人们将内容移动到正确的文件夹，或者没有人使用默认的ASP MVC模板文件夹?
E.g.
如。
1 个解决方案
#1
1
Am I missing something?
我遗漏了什么东西?
Nope.
不。
Do package authors assume that people will move content to the correct folders, or does no one use the default ASP MVC template folders?
包作者是否假设人们将内容移动到正确的文件夹，或者没有人使用默认的ASP MVC模板文件夹?
Pretty much both.
差不多。
There is no guarantee that packages will properly conform to the default ASP.NET MVC template.
不能保证包将正确地符合默认的ASP。净MVC模板。
The authors have probably done it because
作者这么做可能是因为
- As a standalone project, it makes logical sense to put them in such a folder structure.
- 作为一个独立的项目，将它们放在这样的文件夹结构中是合乎逻辑的。
- The project may be trying to be generic across many platforms. In this case it doesn't fit with MVC too well.
- 这个项目可能尝试在许多平台上通用。在这种情况下，它不太适合MVC。
#1
1
Am I missing something?
我遗漏了什么东西?
Nope.
不。
Do package authors assume that people will move content to the correct folders, or does no one use the default ASP MVC template folders?
包作者是否假设人们将内容移动到正确的文件夹，或者没有人使用默认的ASP MVC模板文件夹?
Pretty much both.
差不多。
There is no guarantee that packages will properly conform to the default ASP.NET MVC template.
不能保证包将正确地符合默认的ASP。净MVC模板。
The authors have probably done it because
作者这么做可能是因为
- As a standalone project, it makes logical sense to put them in such a folder structure.
- 作为一个独立的项目，将它们放在这样的文件夹结构中是合乎逻辑的。
- The project may be trying to be generic across many platforms. In this case it doesn't fit with MVC too well.
- 这个项目可能尝试在许多平台上通用。在这种情况下，它不太适合MVC。