Web Studyaspnet.blogspot.com Babyneed.blogspot.com

ASP.Net Web Developer Guide

Power By: eXTReMe Tracker Powered by Blogger  
 
 
 
 

 

 
Important Links
 
   
     
 
Sitemap
 
   
   
 
Reference
 
   

Wednesday, January 25, 2006

Comparing Improvements in ASP.NET to Previous ASP Models (Chapter 1)

The first difference an experienced ASP developer will notice is that VBScript support has been dropped in favor of VB.NET. This is not as much of a hurdle as it sounds like, as the syntax is quite similar, and VB.NET is a full-fledged language and so provides a lot richer environment than VBScript ever could.
As described above, all ASP.NET languages are object oriented, event driven, and server compiled. This brings many benefits, especially where improvements were needed most, namely performance, stability, scalability, and manageability. With Classic ASP, you pretty much had to code your whole application from scratch.ASP.NET has several labor-saving additions to make life easier. Web forms introduce a new Visual Basic Rapid Development-style way of looking at forms in Web pages. With Web Forms, the developer uses new form components that you can add in the traditional way or through code, and they enable the programmer to call on server-side event-driven programming and true separation of layout and logic. You can separate the layout code and functions by using code behind pages that use inheritance to add methods to the form. .NET form controls maintain the session state so the users input remains when the page is submitted,
and the controls’ property values are available to the ASP code without resorting to querying the request object.
The framework foundation class libraries contain exciting new features, previously only available from third parties such as the System. Drawing tools, which enable you to build dynamic images on the fly, built-in browser-based file upload and system network services for working with TCP/IP and DNS. With Web Services and built-in support for SOAP you can distribute code and applications. Your ASP.NET scripts can consume services across the Web, and publish and expose routines as services just as easily.
Deployment, including server configuration, is mostly just a matter of transferring files with configuration that was previously only available from the MMC now implemented with XML files. Now you do not need to register and un-register components, and the server can handle multiple versions of the same component without conflicts.
Mission critical services has increased support with load balancing and several state-management options, including the ability to store state information in an SQL Server database and pass the session ID on the URL to avoid requiring the user to have cookies.

0 Comments:

Post a Comment

<< Home