PROBLEM: Ported working vs2003 Asp.net project to VS2005. Response.Redirect terminates the session.

Environment: W2000 Advanced Server, IIS, vb.net

Both vs 2003 and vs2005 on same machine.

Changed the dll name to appname05.dll so that it would register

I tried the following prior to ‘response.redirect’

Maybe if you use Server.Transfer instead of Response.Redirect?

To my knowledge, the conversion wizard between 2003 and 2005 is not working very well. In my previous projects, the only way to get things working 100% was to recreate all pages in vs2005 and copy-paste the relevant code from the old solution. 

That is an absolute nightmare. In fact, if were not for the fact that sooner or later MS would abandon support for vs 2003 , I wouldn't ever persue this conversion avenue.

Anyone else with an approach to resolve this problem?

Thanks

Well for coversion, you could have followed manual conversion, because its not that straighforward. The other thing is do you really need to convert, because both 2003 i.e. 1.1 and 2.0 application can sit together. Another way is to leave the current app as it is and develop any new ones in .net 2.0 and gradually convert but manually without using automation.

By the way how do you know that session ends on response.redirect?

I know the session ends because, I do cleanups in Session_End. The response.redirect uses a session-specific path that will no longer exist, hence failure.

It becomes extremely complex to maintain a web site using 2 development environments, and in addition have 2 development environments reside on the same machine. The scenario for disaster is that much greater. That, plus the fact that Visual Studio 2005 should as a base, be backwardly compatible, demands that the VS2005 Development Environment WORK. 

To ALL:

I have determined that the Response.Redirect  did not cause Session_termination, but that there is a problem in how Directory.Delete or Directory.CreateDirectory is/are handled in Framework 2.0. The app under Framework 1.1 works fine. 

Response.Redirect was the messenger, revealing what what was happening, at the eariest moment!!

Sorry, barking up the wrong tree. Session_End is the right tree.