As I write this foreword, we are days away from Visual Studio 2005 becoming official. The software
has been “complete” for several months now and the last weeks of the project involve
scouring the code to ensure no rogue bug appears. As the multiple development teams move
their code from their team branches into escrow, the level of anticipation is reaching a
crescendo within the developer community. And rightfully so because for many developers,
ASP.NET 2.0 will revolutionize the way they build software by simplifying many of the common
tasks, in much the same way as ASP.NET 1.0 did for Active Server Page developers.
I recall a similar event when .NET 1.0 was released. Microsoft web developers had to bide
their time with Active Server Pages, which was a great technology at the time, but it was mostly
script based or interpreted. ASP.NET 1.0 changed the way developers thought about writing
their applications. For example, the new Cache API allowed developers to skip the often used
hack of storing commonly accessed data in application state memory; server controls allowed
us to take concepts of reuse found at the component layer and “componentize” the UI. Of
course, there was much, much more, but the biggest improvement by far was that ASP.NET was
built on top of the Common Language Runtime (CLR), providing ASP.NET with a host of benefits
ranging from garbage collection to multiple language support. Here is an interesting piece
of .NET trivia: Did you know that ASP.NET was the first product group within Microsoft to agree
to build their new platform, later to be known as .NET? How far we’ve come…
The planning for .NET 2.0, codenamed Whidbey, began before version 1.0 even shipped,
just as the planning and development for the next version, codenamed Orcas, is already
underway. An interesting aside: If you drive north from Redmond towards Canada, home of
Whistler-Blackcomb—one of the best snowboarding (skiing too) destinations in North
America—there is a restaurant at the base of these mountains called Longhorn (the Windows
Vista codename). On the way to Longhorn, as the crow flies, you’ll pass the city of Everett (codename
of .NET 1.1) and the islands of Whidbey and Orcas.
Every adventure needs a trusted guide. In this exploration of ASP.NET 2.0, whether you are
new to technology or intimately familiar with it, Damon’s book will be a trustworthy
companion. Damon shares his experience as a professional ASP.NET 2.0 software developer
who has not only been studying ASP.NET 2.0 but has used it extensively.
The opening chapters of the book examine defensive programming concepts new to
ASP.NET 2.0, in particular those related to managing the configuration system. The ASP.NET
XML driven configuration system, aka Web.config, not only receives many new settings but
also a programmatic API for managing the system. Although the XML can still be edited
directly, the APIs now allow those settings to be managed through tools as well.
Starting in Chapter 3, Damon begins to explore some of the new user interface features of
ASP.NET 2.0. Master Pages and themes provide us with many more options for customizing the
look-and-feel of our web applications. Damon also examines page skinning, a feature that originated
in ASP.NET Forums (now Community Server) and enables developers to build modular
controls whereby their UI is decoupled from their implementation.
has been “complete” for several months now and the last weeks of the project involve
scouring the code to ensure no rogue bug appears. As the multiple development teams move
their code from their team branches into escrow, the level of anticipation is reaching a
crescendo within the developer community. And rightfully so because for many developers,
ASP.NET 2.0 will revolutionize the way they build software by simplifying many of the common
tasks, in much the same way as ASP.NET 1.0 did for Active Server Page developers.
I recall a similar event when .NET 1.0 was released. Microsoft web developers had to bide
their time with Active Server Pages, which was a great technology at the time, but it was mostly
script based or interpreted. ASP.NET 1.0 changed the way developers thought about writing
their applications. For example, the new Cache API allowed developers to skip the often used
hack of storing commonly accessed data in application state memory; server controls allowed
us to take concepts of reuse found at the component layer and “componentize” the UI. Of
course, there was much, much more, but the biggest improvement by far was that ASP.NET was
built on top of the Common Language Runtime (CLR), providing ASP.NET with a host of benefits
ranging from garbage collection to multiple language support. Here is an interesting piece
of .NET trivia: Did you know that ASP.NET was the first product group within Microsoft to agree
to build their new platform, later to be known as .NET? How far we’ve come…
The planning for .NET 2.0, codenamed Whidbey, began before version 1.0 even shipped,
just as the planning and development for the next version, codenamed Orcas, is already
underway. An interesting aside: If you drive north from Redmond towards Canada, home of
Whistler-Blackcomb—one of the best snowboarding (skiing too) destinations in North
America—there is a restaurant at the base of these mountains called Longhorn (the Windows
Vista codename). On the way to Longhorn, as the crow flies, you’ll pass the city of Everett (codename
of .NET 1.1) and the islands of Whidbey and Orcas.
Every adventure needs a trusted guide. In this exploration of ASP.NET 2.0, whether you are
new to technology or intimately familiar with it, Damon’s book will be a trustworthy
companion. Damon shares his experience as a professional ASP.NET 2.0 software developer
who has not only been studying ASP.NET 2.0 but has used it extensively.
The opening chapters of the book examine defensive programming concepts new to
ASP.NET 2.0, in particular those related to managing the configuration system. The ASP.NET
XML driven configuration system, aka Web.config, not only receives many new settings but
also a programmatic API for managing the system. Although the XML can still be edited
directly, the APIs now allow those settings to be managed through tools as well.
Starting in Chapter 3, Damon begins to explore some of the new user interface features of
ASP.NET 2.0. Master Pages and themes provide us with many more options for customizing the
look-and-feel of our web applications. Damon also examines page skinning, a feature that originated
in ASP.NET Forums (now Community Server) and enables developers to build modular
controls whereby their UI is decoupled from their implementation.
1 comments:
Ada ebook codeigniter advance nggak?
Post a Comment
Please No Junk