ASP.NET is broken down into 3 layers:
- The ASP.NET Application, as the base layer
- ASP.NET Pages
- ASP.NET Web Services
The application represents the entire solution, with ASP.NET Pages representing the user interface, and Web Services exposing selected functionality of the application.
Introducing Web Forms
Web Forms is an ASP.NET technology used on the server to dynamically generate web pages. These pages utilize server-based programmable user interfaces called Web Forms controls that encapsulate common functionality.
ASP.NET Web Forms Framework has been specifically designed to address a number of key deficiencies with the previous model. In particular:
- Reusability of UI controls, which can encapsulate common functionality and reduce the coding
- Allow for creating all application logic on the server, eliminating the need to explicitly code for browser differences
- The ability for developers and designers to work independently -- non-“spaghetti code” – fashion
ASP.NET Web Form Pages are text files with .html filename extension.
Introducing Web Services
A Web Service is a programmable application component that provides a particular functionality, such as a business logic, that is accessible to any number of potentially disparate systems via standard Web protocols such as HTTP, XML, SOAP, and UDDI. ASP.NET Web Form Pages are text files with .asmx filename extension.
Web Services enable the exchange of data in business to consumer (b2c) and business to business (b2b) scenarios, providing access to remotely distributed business applications that can be manipulated from a variety of Internet-enabled clients and devices.
A Web Service can be used either internally by a single application or exposed externally over the Internet for use by any number of applications. Because it is accessible through a standard interface, a Web Service allows disparate systems to work together as a single Web application.
Besides technology that allows developers to create Web Services, Microsoft .NET Framework provides a sophisticated set of tools and code to consume, or access as a client, these Web Services. Because Web Services are based on open protocols such as the Simple Object Access Protocol (SOAP) and HTTP, this client technology can also be used to consume non-ASP.NET Web Services. Of course, the level of integration between ASP.NET Web Services and the client technology is extremely high.
Summary:
ASP.NET is a powerful, strongly typed language, so developers can have a choice of language which best suits them. A vast set of server controls enables quick development time, and easily customizable, browser-safe output. Deploying is no more a problem with XCOPY on our way which makes it easy and simple. Both ASP and ASP.Net can run in parallel, which reduces the need for new hardware dedicated to ASP.NET. |
