ASP.NET MVC默认的项目结构和脚本文件夹 [英] ASP.NET MVC Default Project Structure and the Scripts Folder

问题描述

有什么优势，而使脚本文件夹，它是默认的ASP.NET MVC项目结构。

Is there any advantage to leaving the Scripts folder where it is in the default ASP.NET MVC Project structure.

在我的脑海里会更有意义下的内容文件夹下创建子文件夹为脚本，CSS文件和图像。

In my mind it makes more sense to create subfolders for scripts, css files, and images under the Content folder.

任何缺点这样做？

推荐答案

总之，没有，没有真正的缺点这样做。这就是我一直在构建我的MVC项目。

In short, no, there is no real downside to doing this. It is how I have been structuring my MVC projects.

有一些优势，这样做，其实......在许多项目上我提供了所有的静态内容从一个单独的域，所以把所有的静态内容到一个单独的文件夹中取得了QA /生产部署过程变得更加容易（因为我们脚本部署的MSBuild的和呼叫中缩小实用程序的CSS和JavaScript文件）。

There are some advantages to doing this, actually... on many projects I am serving up all of the static content from a separate domain, so grouping all of the static content into a single folder has made the QA/production deployment process much easier (since we are scripting deployments with MSBuild and calling out to minify utilities for the CSS and Javascript files).

这篇关于ASP.NET MVC默认的项目结构和脚本文件夹的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！