ASP.NET Architecture, Part 1

(Page 1 of 8 )

In this first of a two-part series, Dwight takes us through the new ASP.NET Architecture. We learn about ASP.NET's System.Web.UI namespace classes, interfaces, enumerations, and delegates. We also learn about the ASP.NET page class, including a close look at the life cycle of an ASP.NET page, applying page directives, and the code-behind feature. This piece comes from chapter six of this month's Developer Shed Writing Contest prize, .NET & J2EE Interoperability, by Dwight Peltzer (McGraw-Hill/Osborne, ISBN 0-07-223-054-1, 2004).

---

 

ASP.NET is not just an upgrade to classic ASP but is completely rebuilt from top to bottom. Yet, many familiar ASP features remain, such as Request and Response objects, Application, and Server. You can use the ubiquitous <script runat = “server”> block or ASP <% %> script delimiters, among other familiar items. Microsoft designed ASP.NET so developers who are accustomed to creating applications with classic ASP can continue to do their work while becoming familiar with ASP.NET. Although you may have much time invested in writing legacy ASP applications, ASP.NET applications can run side by side with classic ASP. This is possible because .NET assemblies are not registered in the system registry. Moreover, if you do need to interact with a COM object from ASP.NET, the CLR allows you to do so by generating a runtime callable wrapper (RCW). The RCW functions as a proxy for unmanaged code.

You can also call an ASP.NET object from COM. Again, the runtime generates a COM callable wrapper (CCW). This is good news for developers. You need not abandon your legacy code and applications. Interoperability in the .NET environment between COM objects and managed code is provided by the CLR. The ASP.NET Framework serves as the foundation for creating both web services and browser-based applications and, as mentioned in Chapter 5, has two separate parts, the Common Language Runtime (CLR), which provides support for .NET-hosted applications, and class libraries, which play host to three distinct components:

1. ASP.NET implements the Internet segment of the Framework.
2. ADO.NET provides access to SQL Server 2000.
3. Web forms lend support for smart-client user interfaces.

ASP.NET’s features for enhancing web page development, combined with the .NET Framework’s support for web services, make it the perfect tool for building web services:

1. The code-behind model separates HTML (the presentation layer) from program logic (server-side code). This eliminates the dangerous practice of writing spaghetti code that is prone to error.
   
2. An event-driven program model allows you to write your events and create handlers for them.
   
3. Server controls automatically render HTML appropriate for any client browser.
   
4. Server controls manage client state by using ViewState.
   
5. Code is compiled, thereby enhancing performance.
   
6. Application logic can be written in any CLS-compliant programming language, such as Visual Basic .NET, Managed C++ .NET, or C# .NET.
   
7. Web form development is simplified by using Visual Studio .NET as a RAD tool.

Let’s look under the hood and see how you benefit by migrating from classic ASP to ASP.NET.

Come back this Friday, 27/02/2004, for part two of ASP.NET Architecture. This is chapter six of .NET & J2EE Interoperability, by Dwight Peltzer (McGraw-Hill/Osborne, ISBN 0-07-223054-1, 2004). Buy this book now.

Next: ASP.NET Namespaces >>
 

More ASP.NET Articles
More By McGraw-Hill/Osborne

Comments On: ASP.NET Architecture, Part 1

>>> Be the FIRST to comment on this article!