Part of the ASP.NET vNext initiative, ASP.NET MVC 6 represents a fundamental change to how Microsoft constructs and deploys web frameworks. The goal is to create a host agnostic framework that eliminates the dependencies on the legacy System.Web infrastructure.

　　ASP.NET MVC 6作為ASP.NET vNext解決方案的一部分,，體現(xiàn)了一個(gè)根本性的改變——微軟如何構(gòu)建和部署web應(yīng)用,。它的目標(biāo)是：創(chuàng)建一個(gè)宿主無關(guān)的框架,，以便消除對(duì)傳統(tǒng)的System.Web程序集的依賴,。

　　Microsoft feels that System.Web needs to be removed because it is actually quite expensive. A typical HttpContext object graph can consume 30K of memory per request. When working with small JSON-style requests this represents a disproportionately high cost. With MVC 6 new design, the pre-request overhead drops to roughly 2K.

　　微軟認(rèn)為System.Web需要被移除，因?yàn)樗趯?shí)際使用中相當(dāng)昂貴,。在每次請(qǐng)求中,，一個(gè)典型的HttpContext對(duì)象圖會(huì)占用30K內(nèi)存。這與使用JSON通信相比,，造成不成比例的高成本,。MVC 6力求將“預(yù)請(qǐng)求”的開銷下降到大約2K。

　　Included in MVC 6 is Web API and Web Pages, allowing Microsoft to remove a lot of the overlap between the three frameworks. One result of this change means that MVC will be self-hosting just like Web API 2 and SignalR 2.

　　MVC6中包含Web API,，Web Pages,，微軟移除了框架中重復(fù)的部分，這種變化意味著MVC 6將是自托管的,，如同Web API 2和SignalR 2,。

　　In order to make deployment easier and more reliable, “vNext will support true side-by-side deployment.” Rather than being installed in the GAC, each MVC library needed for a given web site will be referenced like a normal developer-created DLL. “That means you can update your app without affecting other applications on the same server.”

 　　為了使部署更容易和可靠，vNext將支持真正的并行部署,。使用MVC 6構(gòu)建網(wǎng)站時(shí),，站點(diǎn)依賴的程序集不會(huì)安裝在GAC中而是和開發(fā)者創(chuàng)建的DLL類似。這意味著你可以更新你的應(yīng)用,，而不會(huì)影響同一服務(wù)器上的其他應(yīng)用,。

Pay As You Go （現(xiàn)收現(xiàn)付）

　　MVC 6 is built on a “pay as you go” philosophy. Each feature that you wish to use has to be explicitly turned on in the application startup routine. Even serving up static files requires calling IBuilder.UseStaticFiles.

　　MVC 6的設(shè)計(jì)體現(xiàn)了“現(xiàn)收現(xiàn)付”理念。你希望使用的每一個(gè)功能都會(huì)在應(yīng)用啟動(dòng)程序中開啟,。甚至提供靜態(tài)文件需要調(diào)IBuilder.UseStaticFiles,。

　　The way this works is that each website needs to have a class named Startup and this class must have a method called “void Configure (IBuilder app)”. Inside this method you can call functions such as “app.UseServices” to enable features such as MVC.

　　其工作原理是：每個(gè)站點(diǎn)都需要有一個(gè)名為Startup的類，這個(gè)類有一個(gè)方法“void Configure (IBuilder app)”方法,。在該方法中可以調(diào)用你需要的功能方法,，如“app.UseServices”,，以便啟動(dòng)某些特性如MVC。

　　Routing is also setup in the Configuration method. MVC 6 routes are similar, but not identical, to MVC 5 routes. For example, a question mark can be added to a fragment to make it optional in MVC 6. In MVC 5 you would use the UrlParameter.Optional value for the same effect.

　　路由也在配置方法中進(jìn)行設(shè)置,。 與MVC 5的路由相比,，MVC 6有些相似，但不完全相同,。例如,，在MVC 6中可以通過追加問號(hào)表示可選參數(shù)，而在MVC 5中,，需要將其默認(rèn)值定義為UrlParameter.Optional來達(dá)到相同的效果,。

Azure and PowerShell Based Deployments （Azure部署和基于PowerShell的部署）

　　Microsoft is still heavily pushing Azure as the standard way to deploy websites. But they have realized that developers are leery of publishing websites directly from Visual Studio. So instead they will generate PowerShell deployment scripts by default. These can then be edited inside Visual Studio, which now has basic tooling support for PowerShell.

　　微軟仍在很大程度上推動(dòng)讓Azure部署成為網(wǎng)站部署的標(biāo)準(zhǔn)方式。但他們已經(jīng)意識(shí)到,，開發(fā)者們都不愿意直接從Visual Studio發(fā)布網(wǎng)站,。所以，作為替代,，默認(rèn)情況下會(huì)生成PowerShell腳本,。在新版Visual Studio中，已經(jīng)包含了一些PowerShell的基本工具,，以便用戶能夠在Visual Studio里編輯那些生成的腳本,。

The Build Process Doesn’t Build （在生成過程中不會(huì)構(gòu)建程序集）

　　In ASP.NET vNext the build process does not actually build anything. No binaries are generated, it merely runs the type checker to ensure you don’t have any errors or warnings that need to be addressed. Instead the code is compiled on the fly in an as-needed basis, much like we already see with ASP.NET Web Pages. This allows for faster iterations, especially over large websites.

　　實(shí)際上，ASP.NET vNext在生成過程中并沒有構(gòu)建任何東西,。不生成任何二進(jìn)制文件,，它只是運(yùn)行類型檢查，以發(fā)現(xiàn)你代碼的編譯時(shí)錯(cuò)誤和警告,。作為代替,，代碼會(huì)在其被需要時(shí)，快速地被編譯,，這種按需編譯代碼的方式,，很像我們所熟知的ASP.NET中的動(dòng)態(tài)編譯機(jī)制。這允許更快的迭代,，尤其是在大型網(wǎng)站中,。

　　If you want actual binaries to be deployed on a server you need to run the package and publish command. Eventually this will offer several options from source code only, which will continue to compile on the fly, all the way up to natively compiled. The latter should have better performance, but could entail a much longer build process.

　　如果你想將二進(jìn)制的程序集部署在服務(wù)器上，需要使用發(fā)布功能,。這種方式將有更好的表現(xiàn),，但也意味著更長(zhǎng)的構(gòu)建時(shí)間。

Many APIs Will Be Moved or Removed （一些API將被移動(dòng)和刪除）

　　As mentioned before, they are reducing the size of HttpContext from roughly 30K per request to 2K per request. This isn’t free, the cost of that is a significantly reduced set of methods on that object and its children. And by the time they are done it is probably not going to be the only API trimmed down in size.

　　正如前面提到的,，既減少HttpContext的大小從大約每個(gè)請(qǐng)求30K到2K,。這不是免費(fèi)得來的，其代價(jià)是減少該對(duì)象及其子對(duì)象中的方法,。當(dāng)他們完成時(shí),，可能改變的不僅僅是大小。

　　In order to make this transition less painful, they intend to develop an FxCop like tool that will detect when legacy APIs calls are being made. While it won’t be able to automatically rewrite your code, it can at least tell you what needs to be changed before migrating to ASP.NET vNext and MVC 6.

　　為了使技術(shù)過渡更為平滑,，微軟打算開發(fā)一個(gè)類似FxCop的工具,，用于檢測(cè)遺留的API調(diào)用。雖然它不能自動(dòng)重寫你的代碼,，它至少可以告訴你需要遷移到ASP.NET vNext和MVC 6前要改變什么,。

　　Sometimes the change will just involve calling a different method from an optional package or library. Other times the code will need to be significantly rewritten. Since the product is still in alpha a complete list of these changes is not yet available.

　　有時(shí)，變化僅僅是調(diào)用新的程序集或包中的方法,。而其它時(shí)候,，代碼可能需要大量重構(gòu)。由于該產(chǎn)品仍然處于alpha階段,，這些變化的具體內(nèi)容尚不可知,。

Full Framework vs Cloud Optimized Framework （完整的Framework VS 云優(yōu)化的Framework）