ASP.Net has many advantages over Classic ASP, and is much more powerful
overall, but the additional power requires a corresponding amount of work to
master. For one thing, ASP.Net is object-oriented, and that means a lot. If
you're not familiar with OOP, I suggest you read up on it. The advantages of
OOP over procedural programming are many. Basically, OOP extends the idea of
functions and structures in procedural programming, which are based on the
idea of creating reusable "components" that you can employ without having to
re-invent the wheel for every new project. Objects are encapsulations of
both process and state, with extra features built in that simplify
programming overall. But I digress.
It isn't necessary to jump on the ASP.Net bandwagon immediately, but at some
point you will have to adapt to the new object-oriented paradigm. The
procedural paradigm does not have legs any more, and Classic ASP, along with
other procedural technologies will, for most of us, die out in a few short
years.
ASP.Net uses a programming model which is more strict than the Classic ASP
programming model. This has both positive and negative consequences, but the
positives outweigh the negatives by a long shot. On the negative side, you
have to familiarize yourself with the programming model, the Control
LifeCycle, and the dozens of essential classes that are used. You are
generally going to be working at a much higher level of abstraction. Once
you have learned the programming model, and familiarized yourself with the
various Controls, patterns, and practices of ASP.Net, it becomes much
easier. You also have the advantage of working in a medium for which there
are stricter standards, which means that not only will your code be more
extensible and reusable, but it will fit in better with the code of other
ASP.Net developers. This can come in handy when you work with a team or
another contractor, and when you need help in the form of a tutorial or a
pre-built component. The strictness of ASP.Net has all of the same
advantages that the strictness of XHTML has over traditional HTML.
ASP.Net works well in any browser, and has capabilities of adapting the HTML
it renders to specific browsers.
As for flexibility, you can get all the flexibility you need out of ASP.Net.
You can go anywhere you want to go, and do anything you can imagine. You are
not confined to using ASP.Net Controls at all times, and indeed, the ASP.Net
programming model employs "static" HTML as an integral part.
Again, you don't have to suddenly move into it. I would suggest
familiarizing yourself with it over a period of time and making a gradual
transition.
--
HTH,
Kevin Spencer
Microsoft MVP
Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net
"Shawn Ramirez" <ShawnRamirez@discussions.microsoft.comwrote in message
news:2B4383EF-7534-4B34-9933-A0113B50A780@microsoft.com...
Quote:
>I am coming at the world from the standpoint of a veteran ASP Classic
developer. I am not clear on the advantages of using the ASP.NET control
over standard HTML control.
>
With the ASP.NET controls the rendered names are changed and I appear to
be
limited in what javascript events I can fire. I also can not seem to
figure
out how to setup a onsubmit() event.
>
With standard HTML I can setup any javascript event I want and the names
don't change. I can also use multiple forms and do onsubmit().
>
To go along with this I haven't figured out the advantage of the
validation
controls. It looks to me like it renders a new javascript library file
that
is generated dynamically every time the page fires.
>
In my ASP classic developement I have a set of library files/functions
that
handles validation and then displays a nice validation message as well as
changes the label color for input fields.
>
Many of my forms make use of a great deal of dhtml to hide/show different
elements on the page as needed. I make use of callbacks so I don't ever
have
to do a postback because I don't want the redraw and I don't want to have
to
try to setup the page (tabs, show/hide elements, expand/collapse parts of
trees) to do validation.
>
Can I get this kind of flexibility out of asp.net controls? Or should I
stick with HTML controls and using the good old request.form() on post
back?
>
Lastly, the market that I develope for uses browser from IE5 Mac up
throught
IE7. So I can't have solutions that don't work on all browsers. (I might
be
able to abandon IE5 Mac, but Safari will have to stay).
>
I would love any input you all have. I am trying to understand this new
world and don't want to sell any part of it short because it doesn't look
like what I am used to.
Thanks,
Shawn Ramirez
www.dynacal.com 
