Getting Started With Aspnet

State and Application

ASP.NET provides a simple framework that enables Web developers to write logic that runs at the application level. Developers can write this code in either the global.asax text file or in a compiled class. This logic can include application-level events, but developers can easily extend this framework to suit the needs of their Web application. ASP application code, written in the global.asa file, is supported in ASP.NET. You can simply rename global.asa to global.asax when upgrading from ASP.


ASP.NET configuration settings are stored in XML-based files, which are text files easily accessible for reading and writing. Each of your applications can have a distinct configuration file. You can extend the configuration scheme to suit your requirements.


The .NET Framework and ASP.NET provide default authorization and authentication schemes for Web applications. You can easily remove, add to, or replace these schemes depending upon the needs of your application.

Data Access

Accessing databases from ASP.NET applications is a common technique for displaying dynamic information to Web site visitors. ASP.NET makes it easier than ever to access databases for this purpose and provides for managing the data in the database.

Migration from ASP to ASP.NET

Simple ASP pages can easily be migrated to ASP.NET applications. ASP.NET offers complete syntax and processing compatibility with ASP applications. Developers simply need to change file extensions from .asp to .aspx to migrate their files to the ASP.NET framework. They can also easily add ASP.NET functionality to their applications with ease, sometimes by simply adding just a few lines of code to their ASP files. For additional information on handling migration issues, see page 282.


A big difference between ASP 3.0 and ASP.NET is how your code is run on the server. With ASP.NET, your code is compiled into executable classes. With ASP 3.0, code often needs to be interpreted. With ASP 3.0, any serverside code is most likely going to have to be interpreted by the Web server, unless it is cached. If you want to avoid interpreted code in ASP 3.0, you need to put the code into a COM component.


With ASP.NET, you now have access to the common language runtime (or CLR). Running on the CLR gives access to many of the features available in the .NET Framework, such as debugging, security, data access, language interoperability, and more.

Was this article helpful?

0 0

Post a comment