Mystery wrote:
Sorry for the newbie question, but I've only ever needed to use good
ol'fashioned ASP in the past! If it ain't broke, don't fix it!!!
Barry,
Classic ASP is broken! ;-) At least you have to write more classic ASP code
than with ASP.NET code. For example with ASP.NET, you no longer have to
pull the value(s) out of the FORM variable(s) on POSTBACK, and then repopulate
the controls! ASP.NET does this for you automatically now!
Plus the state of each WebControl / WebPage are controlled for you automatically
now by ASP.NET. For example the DropDown Item selection (state) is maintained
for you by ASP.NET on POSTBACK. Hence you no longer need to write the code
to re-select the user selected dropdown item on POSTBACK!
Plus you no longer need to use Response.Write calls. With ASP.NET, you just
read/write to/from the WebControl's properties. e.g. txtLastName.Text = "Prothman"
Plus now you have compiled code in ASP.NET (either 'in-line' with ASPX file,
which is compiled at run-time, hence no DLL, just upload new ASPX page),
or in '*.vb' or '*.cs' code-behind files, which get compiled into a Project DLL
in the BIN directory. Either way, no more slow VBScript code! ;-)
My recommendation is to move to ASP.NET with .NET Framework 1.1
and SQL Server 2000 on Windows Server 2003 machines with IIS 6.0.
For more ASP.NET Paradigm Shifts, check out the following::
http://www.able-consulting.com/dotne...iles/frame.htm
--
Thanks,
Carl Prothman
Microsoft ASP.NET MVP
