Hi Kyle,
good reading if you are thinking about switching over to .net
http://www.powerasp.com/content/new/...-aspdotnet.asp
just one opinion but some good points
Interesting, but I'd like to have seen more comparisons of the actual
technologies used, and also harder hitting questions on how it fits with
future strategies.
One thing that is of special interest to me, is where you say that ASP
is better for the novice developer and .NET is more advanced. This is
the opposite to a) how it's being sold by Microsoft, b) how our own
developers view it.
With .NET (and assuming you have Visual Studio) you can just drag and
drop a few controls onto a form, hit build, and then the app will run
with very little coding, and even when you need to code, you'll get all
that cosy intellisense to help you. Much easier than manually typing ASP
code in notepad! Once it comes to so-called "business objects", how many
classic ASP guys are able to write a COM middle-tier with the correct
threading model etc? .NET does it all for you...
However, I'm there doing all the IIS stuff and knowing what to do when
it gives a cryptic error, and maybe that's where some developers can't
cut it. I also tend to use ASP for my own projects because I find .NET
is like a big glossy facade, but some of these new .NET developers have
lost sight of how the web actually works and they never really
understood Windows so-called "security" in the first place.
One downside of ASP though (relevant to the subject) is that you can end
up re-inventing the wheel all the time (e.g. making a data grid) whereas
..NET has a lot of pre-built kiddie-bricks you can play with out of the box.
--
Gerry Hickman (London UK)