简体   繁体   English

将生产服务器从ASP.NET 2升级到ASP.NET 4

[英]Upgrade production server from ASP.NET 2 to ASP.NET 4

I have a production server (Windows Server 2003 SP2), running several ASP.NET 2 apps under IIS6. 我有一个生产服务器(Windows Server 2003 SP2),在IIS6下运行几个ASP.NET 2应用程序。 New applications are developed using ASP.NET MVC 3 (Razor) and Entity Framework 4. Old applications are not to be touched. 使用ASP.NET MVC 3(Razor)和Entity Framework 4开发了新的应用程序。不应触及旧的应用程序。

Clearly, the following components need to be upgraded: 显然,需要升级以下组件:

  • .NET framework (install 4.0 side by side with existing 1.0, 2.0, 3.5SP1) .NET框架(与现有的1.0,2.0,3.5SP1一起安装4.0)
  • ASP.NET (install v.4 side by side with 2.0) ASP.NET(与2.0并排安装v.4)

I want to keep IIS6 to avoid surprises, but it needs to be configured for MVC 3 routing 我想保留IIS6以避免意外,但需要为MVC 3路由配置它

Which installer(s) is the most appropriate in this case? 在这种情况下哪种安装程序最合适? There are too many different ones available from MS - full, client profile, web platform installer etc :( Goal number one is the not to break existing apps and keep downtime to a reasonable minimum. MS中有太多不同的可用 - 完整,客户端配置文件,网络平台安装程序等:(目标第一是不破坏现有应用程序并将停机时间保持在合理的最低限度。

Use the Web Platform Installer; 使用Web平台安装程序; it's specifically meant to help you get exactly what you need to run things. 它专门用于帮助您准确掌握运行所需的内容。 In your case, it will install the full .NET 4.0 Framework, and the other things you need, assuming you make the correct selections with it. 在您的情况下,它将安装完整的.NET 4.0 Framework,以及您需要的其他内容,假设您使用它进行正确的选择。

Installing any of the components you speak of will not do anything to your existing applications, provided you don't misconfigure them in such a way as to improperly attempt to use the new frameworks. 安装您所说的任何组件都不会对现有应用程序执行任何操作,前提是您不会错误地配置它们以便不正确地尝试使用新框架。 All of this stuff works side-by-side by default. 默认情况下,所有这些东西并排运行。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM