>I don't understand "ASP becomes unwieldy when an application moves from simple to more complex" as I have read here on the UT a number of times. Poor ASP coding techniques becomes no more "unwieldy" then a poorly written FoxPro application. Good coding techniques and well written documentation should be the norm for any language. Then the platform doesn't get "unwieldy". That being said ...

Oh man, you have to be kidding right?

Yes, good coding will help, but not much. I don't care how much you organize
your code you'll end up with code in places where it doesn't belong with
ASP. Keeping things organized and efficient is a bitch... and that's
if you're actually trying.

I look at a lot of code that is produced and ASP code is some of the worst
I've seen in any kind of development. And this even by otherwise good
developers that are aware of coding standards and organizing skills for
code.

Moving to complex Web applications with ASP is a huge step from a simple
two page app. Much more so than any other development environment.
I don't think ASP was ever meant to be the end all solution for code -
I'm certain the idea was that ASP was to be a vehicle as a COM client
to keep business logic where it belongs - in objects.

Moving to COM is a bear too - registering components, moving them around
managing the Web server to update code - synching sites. It far from
straight forward.

Then there's the whole gig of how the COM threading models work in
ASP - which is utterly mis/underdocumented and ends up killing performance
of many COM based applications. ASP apps work well when properly
configured - but watch out for those that aren't.

Believe me, I think ASP is a decent platform for Web development, but
it sure ain't easy when it comes to building anything but trivial apps,
especially those that require COM.

+++ Rick ---