Link to home
Start Free TrialLog in
Avatar of ksd123
ksd123

asked on

Migrating from IIS6 to IIS7

Hi Experts,

We have  a legacy .Net Application (Asp.net 2.0,.Net Framework 2.0,VS 2005) hosted on IIS6 (windows server 2003)  working fine without any issue.Now we want to migrate the application to  IIS7 (windows server 2008).I am getting error at Global.asax when I select application pool pipeline mode as "integrated " in IIS7 and this error r is due to a design change in the IIS7 Integrated pipeline .I resolved this error just by changing app pool pipeline mode to "classic" and working fine.

I googled on this issue some recommend "classic" without changing any code and others recommend "Integrate" mode and for this I need to change the code at Global.asax file.

Can anyone guide me which approach should I opt and what are the implications of using one over  the other? (classic vs integrated)


Thanks in Advance
ASKER CERTIFIED SOLUTION
Avatar of Bob Learned
Bob Learned
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Then, ask yourself why you are going to IIS7?  I always like to run in Integrated Mode, so I would investigate what you are using in the Global.asax, that requires IIS 6 worker-process isolation mode (Classic), and see if there is a different approach.
Avatar of ksd123
ksd123

ASKER

Thanks for the explanation