RAM and CPU % is the only consideration. If your machine is already really busy serving ASP pages and with IIS (say 90% CPU and 90% RAM full) taht only leaves 100% for the ASP,net Worker Process.
So more RAM may help but if your machine is serving ASP fine it can serve ASP.net fine too. But unlike Classic ASP which is 2-way real time coupled to IIS (if IIS dies ClassicASP dies, if a bad script kills Classic ASP it will hurt IIS) ASP.net is only vaguely connected to IIS. x.aspx comes in IIS looks at it and hand it to Asp.net worker process (WP) later when ASP.net WP is done with page it throws back finished HTML to IIS IIS could have even been stopped and restarted in the middle of that and ASP.net does not care -- when it comes back up it hands it the HTML. x.asp comes in and can't function till IIS hands it 6 objects (response, request, etc.) and while the page is being processed IIS and Classic ASP talk constantly share memory and are what we call tightly coupled. On Tue, 21 Dec 2004 16:14:07 -0000, slitineh <[EMAIL PROTECTED]> wrote: > > > Hi! HAPPY HOLIDAYS, folks! > > I would very much appreciate your help with whether it is possible to > use both ASP pages side by side with asp.net pages in the same web > application. Is there any downside in the combination or both live in > harmony with each other. ------------------------ Yahoo! Groups Sponsor --------------------~--> $4.98 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/saFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspClassicAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
