I have an application, App1 in IIS 6, created in its own application pool.
The code is completely written and compiled using ASP.NET 2.0 with C#.
Now I have another request to create a "reports" folder that has code
written in classic asp.
As I am not creating "reports" as application. Do I need to worry about
performance issues or for that matter exception issues?
thanks in advance!
Hi,
My understanding is that you will run both applications in the same
application pool. This means they will share the same resources and if
either one of them misbehaves, it may bring down both applications.
As for performance, it can both positive and negative to run them in the
same application pool. It depends on the applications. If one application
overconsumes resources, it may be better to isolate them. But having
multiple application pools may just waste resources.
If you trust the "reports" code, you can probably run them in the same
application pool as the .NET application.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
"Enthus"
news:0529BF36-8281-41D0-939C-B54A8EBB3763@microsoft.com...
>I have an application, App1 in IIS 6, created in its own application pool.
> The code is completely written and compiled using ASP.NET 2.0 with C#.
>
> Now I have another request to create a "reports" folder that has code
> written in classic asp.
>
> As I am not creating "reports" as application. Do I need to worry about
> performance issues or for that matter exception issues?
>
> thanks in advance!
"Enthus"
news:0529BF36-8281-41D0-939C-B54A8EBB3763@microsoft.com...
> I have an application, App1 in IIS 6, created in its own application pool.
> The code is completely written and compiled using ASP.NET 2.0 with C#.
>
> Now I have another request to create a "reports" folder that has code
> written in classic asp.
>
> As I am not creating "reports" as application. Do I need to worry about
> performance issues or for that matter exception issues?
>
> thanks in advance!
ASP and ASP.NET run quite happily (and oblivious to each other) in the same
AppPool.
There is no need for any extra concern over performance any more than you
would if the new reports feature were also in ASP.NET.
To what are you refering when you say 'exception issues'?
ASP.NET goes a lot further when handling exceptionaly circumstances and
allows its own level of customising responses to 404 for example. ASP on
the other hand relies on the underlying IIS to handle this.
--
Anthony Jones - MVP ASP/ASP.NET