Hi Asaf,
I think Brock's suggestion is reasonable. As for windows 2003 server/IIS6,
it use Application Pool process Isolation model by default. You can think
an application pool as an IIS worker process, so we should separate ASP.NET
1.X application from ASP.NET 2.0 application by putting them into different
application pools.
BTW, I suggest you separate ASP.NET 1.x application from 2.0 applications
into different IIS sites if possible. This is because ASP.NET application's
configuration is hierarchically inherited, and ASP.NET 2.0 configuration
has involved many new configuration elements which are not supported by
ASP.NET 1.x applications. If you put them together ,there will cause some
unexpected configuration parsing error.
Hope this also helps.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)