Datasheet

1 2 3 4 5 6 7 8 9 10
Introduction to ASP.NET 2.0
With the release of ASP.NET 1.0, Microsoft revolutionized web application development by pro-
viding a rich set of features aimed at increasing the productivity of developers. Now with
ASP.NET 2.0, Microsoft has raised the bar to a much higher level by providing excellent out-of-the-
box features that are not only geared toward increasing the productivity of developers but also
toward simplifying the administration and management of ASP.NET 2.0 applications. These new
features, combined with the increased speed and performance of ASP.NET 2.0, arm developers
with a powerful platform that can make a significant impact on the way web applications are
developed, deployed, and maintained.
This chapter takes a quick tour of the new ASP.NET 2.0 features. Specifically, this chapter will dis-
cuss the features of this new, improved platform that will help you in designing, developing, and
deploying enterprise-class web applications.
ASP.NET 2.0 Features
If you have worked with ASP.NET 1.x versions, you will undoubtedly agree that it was a great prod-
uct that provided huge improvements in the way web applications were designed and deployed. If
ASP.NET 1.x was a great product, then what’s wrong with it? Well, nothing, actually, but when devel-
oping software, there is always a trade-off between how much can be done, how many resources you
have, and how much time you have to do it. There is an almost never-ending supply of features you
can add, but at some stage you have to ship the product. You cannot doubt that ASP.NET 1.0 shipped
with an impressive array of features, but the ASP.NET team members are ambitious, and they not only
had plans of their own but also listened to their users. ASP.NET 2.0 addresses the areas that both the
development team and users wanted to improve. The aims of the new version are:
Reduce the number of lines of code required by 70%: The declarative programming
model freed developers from having to write reams of code, but there are still many sce-
narios where this cannot be avoided. Data access is a great example, where the same
Connection,
DataAdapter/DataSet, and Command/DataReader code is used regularly.
05_041796 ch01.qxp 12/29/06 9:09 PM Page 3
COPYRIGHTED MATERIAL

Summary of content (22 pages)