Upgrading From Classic to .net - Questions

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi, 

I've been looking around on the web for variant things to explain to me why upgrading to ASP.net from classic ASP is a good idea.  Now the best points put across are as follows:
Future of web development
Ado.net means that database connections are never kept open when working with datasets.
Compiled rather than interpreted language which translates to quicker load times.
Event driven programming.
User authentication, with accounts and roles
XML based language
And now counter arguments:
No plans for phasing out classic ASP in the near future
Ado also allows for the same principals of hitting a database getting data and closing the database again as shown by the following function:

Function fn_DatabaseGrabrows(strConnection, strSQL)

set rs = getRSet(strConnection, strSQL)

fn_DatabaseGrabrows = null

If NOT rs.eof then fn_DatabaseGrabrows = rs.getRows()

set rs = nothing

End Function

Function getRSet(strConnection, strSQL)

Set ConnX = CreateObject("adodb.connection")

With ConnX

.ConnectionString = strConStr

.Open

.CursorLocation = 3

set RSet0 = .Execute(strExecProc)

End With

Set GetRSet = RSet0

Set ConnX = Nothing

Set RSet0 = Nothing
End Function

From what i can see, because ASP.net is pre-compiled adding additional scripts to it such as adding extra pages as you would with the WWF application is not allowed without re-compiling them.
The event driven programming is all good but still the basis of any web programming language to update anything from the server is still using postbacks / AJAX.
User authentication, aside from the .net passport integration which im guessing could be done using a COM Add-In anyways what part of the .net authentication can't be done using classic ASP.
Simple enough to use XML with the XML components, programmable with createobjects.
Theres also been a big thing made about AJAX interactivity alongside the .net framework, when this is simple enough using client side javascript anyways.

Don't get me wrong im not trying to knock the dot net architecture as Im sure it does have a lot of benefits that outweigh classic ASP, I am however trying to figure these out and would like assistance in what I can do in .net that I can't do in classic.

I checked a video out online but after hearing that ASP classic was a single language where ASP.net is one of serveral compiled languages, I didn't take too much notice of the rest of the video as there were quite a few other inaccuracies.

Any help, pointers and guidance would be appreciated and the feedback from people who have migrated from classic to .net would be really helpful.