迁移Web场到运行asp.net第4版，同时保持会话 [英] Migrating web farm to runtime version 4 of asp.net while maintaining session

问题描述

我们已经迁移了web应用从.NET运行库2（V 3.5），以.NET运行时4（V 4.5），我有部署的问题。
我们的sessionState服务器是一个的StateServer，和一个单独的服务器上运行，从框架2 aspnetsession。当我们部署和升级应用程序池.NET 4中我们在测试Web服务器之一，它似乎会话过期或以某种方式为丢弃我们重定向到我们的应用程序的登录页。

We've migrated our webapplication from .net runtime 2 (v 3.5) to .net runtime 4 (v 4.5) and I have a question for deployment. Our sessionstate server is a "stateserver", and runs aspnetsession from framework 2 on a separate server. When we deploy and upgrade the application pool to .net 4 to one of our webservers in test, it seems that the session expires or is dropped somehow as we're redirected to the logon page of our application.

有没有部署我们的用户在此过程中丢失会话的应用程序我们的新版本的方法吗？是sessioncookie通过应用程序池在.NET 2不兼容捉迷藏使用.NET 4中创建？我看不出这事在破变化白皮书

Is there any way of deploying our new version of the app without our users losing session in the process? Are the sessioncookie created by application pools runnning in .net 2 not compatible with .net 4? I cannot see anything about this in the breaking changes whitepaper

编辑：网站的应用程序路径是一样的，它并没有改变这个版本我们的应用程序，我们已经做了不停工的部署（用户不会注意到新版本，并不会注销）的5-6年约50的版本。

Application Path of the website is the same, it has not changed for this version of our application, and we have done "no-downtime" deployments (users don't notice new version and are not logged out) for 5-6 years with approx 50 releases.

EDIT2：与此相反的是不正确的：在应用程序运行.NET Framework 4创建会话，然后降级到.NET 2不破会话。与此相反的是真实的，但是。

The opposite is not true: Creating session in an application running .net framework 4, and then downgrading to .net 2 does not break the session. The opposite is true, however.

在前进，谢谢你的任何指针

In advance, thank you for any pointers

推荐答案

如何负载均衡农场打造粘性会话坚持现有会话到.NET运行2.0的机器和任何新的会话机.NET 4.0上运行。

How about load balancing the farm to create "sticky sessions" to stick existing sessions to machines running .net 2.0 and any new sessions to machines running .net 4.0.

当然，这取决于是否您的项目将承受在同一时间运行在生产中2不同版本的工程....正如我猜测，不仅有.NET版本的改变，但也潜在$ C $下在您的项目。例如将人从2不同版本的项目数据库修改数据产生影响。

Of course this depends on whether your project will withstand running 2 different versions of the project in production at the same time.... As I'm guessing that not only have the .net versions changed but also underlying code in your project. For example will people modifying data in the database from 2 different versions of your project have an impact.

因此​​，考虑到它运行自己项目的多个版本，而不是.NET版本的会议的问题。在这个角度看它可能使它更容易解决的问题......或更困难:-)这取决于你的项目。

Thus considering it a problem of running multiple versions of your own project, rather than of .net versions' sessions. Looking at it in this angle may make it an easier problem to solve ... or much more difficult :-) depending on your project.

这篇关于迁移Web场到运行asp.net第4版，同时保持会话的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！