Clever Geek Handbook

Why did my ASP.NET application crash after migration?

My web application worked fine on Windows Server 2003 with .NET Framework 2.0. When I migrated to Windows Server 2008 from .NET Framework 3.5.

With the same code as on both servers, the difference between them was as follows: for a given async ASHX (IHttpAsyncHandler), the previous server automatically responded to the request with the Connection and Content-Length headers. Since the new server did not automatically generate these headers with the previous code, I had to change the code to do it manually, otherwise the web clients were unable to detect the end of the response.

My question is, isn't .NET Framework 3.5 supposed to support full backward compatibility with .NET 2.0?

+1


source to share


2 answers


Set ApplicationPool to Classic.



+3


source


The problem is not with the .Net Framework, which is different from IIS7 and IIS6. As stated by leppie , you need to set your application pool to classic mode.



+3


source






More articles:


All Articles