This will probably make a lot of you mad on here, but I just *downgraded* my
websites from ASP.NET to Classic ASP.
Why?
1) The .NET Framework seems to be in a state of flux: Something written for
Version 1.1 will not run on servers using 2.0, 3.0, etc. This translates to
always having to go back and update the code that clients never seem to want
to pay for, and I have to go out there and buy the latest developer that can
handle it. In contrast, Classic ASP can be compared to Latin: It is no
longer a "spoken language" in the development world, yet it seems that every
server out there still understands it.
2) Servers running the latest versions of the Framework are generally more
expensive to rent space on than a server that does not tell you what it is
running or makes no guarantee of what it is running. Classic ASP doesn't
need the Framework, so my clients save monthly upkeep fees.
Why does Microsoft have to be so expensive? Actually, I know: It's all about
the money! Still, it would be nice if we could stick with something that
worked well and enjoy a comfort zone until it did *not* work.
Sorry. I'm rambling. I'll stop now.
"Mark Rae [MVP]" wrote:
"Alexey Smirnov" wrote...
>Well, many enterprises make it a point not to install anything until
the SP1 is released.
Indeed.
>I have a client who is asking me to deliver ASP 2 (a classic one)
solution
Wow! I normally say yes I'll do it, but it's my standard daily rate x 10
(not joking!)
--
Mark Rae
ASP.NET MVP
http://www.markrae.net