|
ASPPlayground -> RE: RE: ASP & ASP.Net (10/6/2002 17:20:20)
|
quote:
ORIGINAL: c1sissy If asp.net is harder to learn, will it be a bit easier after tackling the classic asp? Just curious here. No, I don' t really think so. See, ASP can' t do anything useful without connecting to database first (this is what server-side programming is all about - data driven web page). Therefore, when you learn ASP, you have to learn the ADO model. You will definitely have to memorize a few common ADO techniques to become proficient as an ASP programmer. For example, a few of the recordset object' s methods are used everywhere -> the GetRows method, the MoveNext method, etc. Without the two methods I mentioned here, there is no ASP page. And now, Microsoft has decided to abandon their well known, widely used ADO, and replace it with ADO.NET. In ASP.NET/ADO.NET, everything is about disconnected data, everything is about databinding, and everything is about event-driven programming (and none of the three here are available in ASP/ADO). If you still think you can build a table with the MoveNext method or populate a drop down list with the GetRows method, think again. FYI, there is no recordset object in ADO.NET (not even a .NET equivalent), and there is no movenext nor getrows. As a conclusion, you will be wasting your time familiarizing yourself with the ADO object model if you want to move to ASP.NET very soon. All the " GOOD" database techniques you learn with ADO are considered " BAD" in ADO.NET. If you want to compare ASP/ASP.NET without any of the db thing I mentioned here, chances are you will be very frustrated as well (at least, I was). Pure ASP.NET is " event-driven" (somewhat like the DOM), not procedural (like ASP). My suggestion to you is go ahead and learn ASP.NET: Learn the Page Cycle and Web controls first (they are just like the DOM in my opinion with a few extra tags, like <asp:button>). Do learn viewstate and the postback architecture. Don' t bother with all those Rich Controls first. They all look good, but you just can' t learn everything at once. Just don' t bother with them - don' t even look at what they can do. Forget about " looking for a .NET equivalent technique to classic ASP" . Try to learn DataBinding with the DataReader object. You will want to review many of the data aware web controls at this stage, partucularly the three list controls. Don' t bother with DataSet (DataAdapter, DataView, DataRow, DataColumn) first. They are just too different from the datareader which may confuse you. Write some simple pages displaying records from the Northwind db (using pure .NET with databinding and the datareader object). Learn Code Behind and User Controls. Forget about " includes" . Go back to write those pages again with Code Behind and User Controls, and then always stick with these two techniques. If you just can' t understand why those " protected members" are there (as in code behind), I will suggest that you go look for some reference on " how to write .NET class" . This is an essential part of ASP.NET programming, which you won' t learn from ASP programming. And the list goes on. It is hard to become very proficient in ASP.NET like the way you did in ASP. It is very difficult, and there are many more things to memorize than with the classic ASP. I hope this can help everyone a bit[:)]
|
|
|
|