FAQ Home :
	What are the short commings of Classic ASP Answer Classic ASP has several shorrt commings 1. Interpreted Code is not compiled. Script code is interpreted at run time. 2. Loosely Typed Variable are variants, we did not have integer, strings, boolean, recordset etc loading objects were late bound i.e script had no knowledge of an object properties. You could use a COM object i.e. a DLL to use more complex code, however the upgrade proces as you extended your application was problematic. No way to load the new COM object until you restarted the server or used COM+. 3. UI code vs Backend code were mixed. ASP mixed in the HTML and the ASP ie the code sections that did the ASP workj and thus working together in a project team that did the server side stuff and the User interface i.e the graphics etc. ASP they were imbedded toether. .NET seperates the two. Not very good tool, Macromedia and Visual Interdev and every serious devloper ended up an IDE, but debuggin was always done manually i.e response.write to log values a certain points in the code. This was crude and basic and when JavaScript was mixed. 4. Session state Maintaning session state was in the memory of the webserver. There might be previous sesion state sharing but sometimes the data might be on seperate servers and thus became more complex. So when server farms were added there serialisation needed for state management. 5. IIS Settings ASP used IIS metabase for it's settings but not really programatically available to the code. ie dsettings were machine specific. 6.Postbacks If you have code that needs to process postpbacks, then the ASP code had to store the requets object in variables, but when the page was refreshed the page would go blank unless we used code to preserve the request data write it back out to the screen. 7. Browsers Multibrowsers were an issue we have to sniff for the browser i.e detect and then use different routines appropriately. Attachments -none- Applies to versions FAQ Provided By Steven Charles Robinson Credit